Processed: Re: Bug#921257: khal: FTBFS randomly when built with eatmydata and overlayfs
Processing control commands: > retitle -1 khal: FTBFS randomly when built Bug #921257 [src:khal] khal: FTBFS randomly when built with eatmydata and overlayfs Changed Bug title to 'khal: FTBFS randomly when built' from 'khal: FTBFS randomly when built with eatmydata and overlayfs'. > severity -1 serious Bug #921257 [src:khal] khal: FTBFS randomly when built Severity set to 'serious' from 'normal' -- 921257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953144: origami install fails with "ERROR: WGET RETRIEVAL FAILED!"
On Sat, 07 Mar 2020 23:35:29 +0100 Andreas Beckmann wrote: > Followup-For: Bug #953144 > > origami is missing a dependency on lsb-release (needed for os > identification). > > The URL https://zelut.org/projects/misc/finstall is no longer available > and causes the reported error. > > There is no validation (e.g. hash/signature checking) on the downloaded > bits, which contain code to be executed ... > > BTW, as a downloader package, why isn't this in contrib? > > > Andreas > > I contacted Christer Edward, who owns the site, He has restored the file, but has not maintained it in several years. I'm trying to install on a Raspberry Pi 4 and Jetson nano both running Ubuntu. This isn't going to work for me because to the CPU, but it might work for others running on an x86 platform. Scott
Processed: Tag bug
Processing commands for cont...@bugs.debian.org: > tag 951891 + help Bug #951891 [src:open-ath9k-htc-firmware] open-ath9k-htc-firmware FTBFS with binutils 2.34 Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 951891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 956959 is normal, tagging 956959
Processing commands for cont...@bugs.debian.org: > severity 956959 normal Bug #956959 [xpra] can no longer connect after dist-upgrading server Severity set to 'normal' from 'grave' > tags 956959 + unreproducible moreinfo Bug #956959 [xpra] can no longer connect after dist-upgrading server Added tag(s) moreinfo and unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 956959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952022: marked as done (ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:)
Your message dated Wed, 22 Apr 2020 23:33:38 + with message-id and subject line Bug#952022: fixed in ruby-puppet-syntax 2.6.1-2 has caused the Debian Bug report #952022, regarding ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.7" failed: LoadError: 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.) -- 952022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-puppet-syntax Version: 2.6.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > LoadError: > libfacter was not found. Please make sure it was installed to the expected > location. > cannot load such file -- libfacter.so > # ./lib/puppet-syntax/templates.rb:2:in `' > # ./lib/puppet-syntax.rb:3:in `' > # ./spec/spec_helper.rb:2:in `' > # ./spec/puppet-syntax_spec.rb:1:in `' > # -- > # --- Caused by: --- > # LoadError: > # cannot load such file -- libfacter.so > # ./lib/puppet-syntax/templates.rb:2:in `' > No examples found. > > Finished in 0.3 seconds (files took 0.19211 seconds to load) > 0 examples, 0 failures, 5 errors occurred outside of examples > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/02/22/ruby-puppet-syntax_2.6.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: ruby-puppet-syntax Source-Version: 2.6.1-2 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-puppet-syntax, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated ruby-puppet-syntax package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 Mar 2020 18:54:53 +0100 Source: ruby-puppet-syntax Architecture: source Version: 2.6.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Daniel Leidert Closes: 952022 Changes: ruby-puppet-syntax (2.6.1-2) unstable; urgency=medium . * Team upload. * d/control (Build-Depends): Add ruby-rspec (closes: #952022). (Depends): Require puppet >=5. * d/rules: Add override to install upstream CHANGELOG.md. Disable verbose mode. Use the gem installation layout. * d/patches/0002-marks-tests-pending.patch: Add new patch. - Mark tests failing because of an unrelated puppet warning as pending. This finally fixes #952022. * d/patches/series: Enable new patch. * d/upstream/metadata: Add metadata. Checksums-Sha1: 0cb7adb34709ab5b1ea100bcebbade2618006b23 2217 ruby-puppet-syntax_2.6.1-2.dsc 4d50492eb2581a31372eb6c074bdf356b14ed2de 4324 ruby-puppet-syntax_2.6.1-2.debian.tar.xz 3c570820267f0395320c6cd4dc92b7b8e69dc5ff 9974 ruby-puppet-syntax_2.6.1-2_amd64.buildinfo Checksums-Sha256: 56c42ba673ae20cc3db1070f5a37c7d7d23a7296cba53c77f029133c6f628196 2217 ruby-puppet-syntax_2.6.1-2.dsc e3a7c6397feeaa8f769f0b71c0b44e90be3904c0072595771a2d6eae8faf9113 4324 ruby-puppet-syntax_2.6.1-2.debian.tar.xz 515117b6e4eebc009f64fd462b74321c9d53418e46c27904bd1987ae1a85f928 9974 ruby-puppet-syntax_2.6.1-2_amd64.buildinfo Files: 7f87e137e2a1c0d131aae614d3f3bf05 2217 ruby optional ruby-puppet-syntax_2.6.1-2.dsc ea4a351b5446e9dac9b7115f38e1acf7 4324 ruby optional
Bug#958499: eclipse: fails to launch
Package: eclipse Version: 3.8.1-11 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? 1. `sudo apt install eclipse` 2. Launch Eclipse from the menu or from commandline. 3. I get 'An error has occurred.' There is a log generated: !SESSION Wed Apr 22 16:16:35 PDT 2020 -- !ENTRY org.eclipse.equinox.launcher 4 0 2020-04-22 16:16:35.306 !MESSAGE Exception launching the Eclipse Platform: !STACK java.lang.ClassNotFoundException: org.eclipse.core.runtime.adaptor.EclipseStarter at java.net.URLClassLoader.findClass(URLClassLoader.java:382) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:626) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) at org.eclipse.equinox.launcher.Main.run(Main.java:1438) at org.eclipse.equinox.launcher.Main.main(Main.java:1414) * What exactly did you do (or not do) that was effective (or ineffective)? After Googling this error, it was suggested to explictly specify Java8 in eclipse.ini. * What was the outcome of this action? The problem is still the same. Additional Googling suggests this package is 1) very outdated, and 2) hopelessly broken. Eclipse Founation itself does not provide this for the armv7l architecture. * What outcome did you expect instead? A package provided in repos should work. It should probably be removed from the repos to save other users the frustration. -- System Information: Distributor ID: Raspbian Description:Raspbian GNU/Linux 10 (buster) Release:10 Codename: buster Architecture: armv7l Kernel: Linux 4.19.97-v7+ (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages eclipse depends on: ii eclipse-jdt 3.8.1-11 ii eclipse-pde 3.8.1-11 eclipse recommends no packages. eclipse suggests no packages. Versions of packages eclipse-platform depends on: ii ant 1.10.5-2 ii ant-optional 1.10.5-2 ii default-jre [java6-runtime] 2:1.11-71+b1 ii eclipse-platform-data3.8.1-11 ii eclipse-rcp 3.8.1-11 ii gconf-service3.2.6-5 ii java-common 0.71 ii libc62.28-10+rpi1 ii libcommons-codec-java1.11-1 ii libcommons-httpclient-java 3.1-15 ii libcommons-logging-java 1.2-2 ii libgconf-2-4 3.2.6-5 ii libglib2.0-0 2.58.3-2+deb10u2 ii libjetty9-java 9.4.15-1 ii libjsch-java 0.1.55-1 ii liblucene2-java 2.9.4+ds1-6 ii libservlet3.1-java [libservlet3.1-java] 1:4.0.1-2 ii openjdk-11-jre [java6-runtime] 11.0.6+10-1~deb10u1 ii openjdk-8-jre [java6-runtime]8u212-b01-1+rpi1 ii sat4j2.3.5-0.3 Versions of packages eclipse-platform recommends: ii eclipse-pde 3.8.1-11 Versions of packages eclipse-platform suggests: ii eclipse-jdt 3.8.1-11 Versions of packages eclipse-pde depends on: ii default-jre [java6-runtime] 2:1.11-71+b1 ii eclipse-jdt 3.8.1-11 ii eclipse-platform3.8.1-11 ii libasm3-java3.3.2-3 ii openjdk-11-jre [java6-runtime] 11.0.6+10-1~deb10u1 ii openjdk-8-jre [java6-runtime] 8u212-b01-1+rpi1 eclipse-pde suggests no packages. Versions of packages eclipse-jdt depends on: ii default-jre [java6-runtime] 2:1.11-71+b1 ii eclipse-platform3.8.1-11 ii junit 3.8.2-9 ii junit4 4.12-8 ii libhamcrest-java1.3-9 ii openjdk-11-jre [java6-runtime] 11.0.6+10-1~deb10u1 ii openjdk-8-jre [java6-runtime] 8u212-b01-1+rpi1 Versions of packages eclipse-jdt recommends: ii default-jdk 2:1.11-71+b1 eclipse-jdt suggests no packages. -- no debconf information
Bug#958497: geoclue-2.0 violates GDPR
Package: geoclue-2.0 Version: 2.5.6-1 Severity: serious The geoclue package collects SSIDs in the neighborhood and sends them to Mozilla location services. The SSID of an adhoc network (which for instance is set up for tethering via a mobile phone) is personally identifiable information. Sending this information about a third person without his or her explicit consent to another party especially one outside of the European Union is in breach of the German law Datenschutz-Grundverordnung which is the German implementation of the European General Data Protection Regulation (GDPR). The easiest remedy would be to remove the package from the repository until it is fixed upstream to be compliant. Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924516 src/gclue-config.c:219: #define DEFAULT_WIFI_URL "https://location.services.mozilla.com/v1/geolocate?key=; MOZILLA_API_KEY #define DEFAULT_WIFI_SUBMIT_URL "https://location.services.mozilla.com/v1/submit?key=; MOZILLA_API_KEY Best regards Heinrich Schuchardt
Bug#956598: marked as done (ruby-combustion autopkgtest is failing with NoMethodError: undefined method `expect' for #)
Your message dated Wed, 22 Apr 2020 22:49:06 +
with message-id
and subject line Bug#956598: fixed in ruby-combustion 1.1.1-3
has caused the Debian Bug report #956598,
regarding ruby-combustion autopkgtest is failing with NoMethodError: undefined
method `expect' for
#
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.)
--
956598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-combustion
Version: 1.1.1-2
Severity: serious
Failures:
1) Combustion::Database returns test database for model with default
connection
[31mFailure/Error: expect(Model.connection_config[:database]).to
match(/test/)[0m
[31m[0m
[31mNoMethodError:[0m
[31m undefined method `expect' for
#[0m
[31m Did you mean? exec[0m
[36m# ./spec/database_spec.rb:24:in `block (2 levels) in
'[0m
2) Combustion::Database creates dummy table from migration in base
database
[31mFailure/Error:
expect(Model.connection.table_exists?("dummy_table")).to eq true[0m
[31m[0m
[31mNoMethodError:[0m
[31m undefined method `expect' for
#[0m
[31m Did you mean? exec[0m
[36m# ./spec/database_spec.rb:12:in `block (2 levels) in
'[0m
3) Combustion::Database creates another dummy table from another
database
[31mFailure/Error:[0m
[31m
expect(ModelInAnotherDb.connection.table_exists?("dummy_table")).[0m
[31m to eq false[0m
[31m[0m
[31mNoMethodError:[0m
[31m undefined method `expect' for
#[0m
[31m Did you mean? exec[0m
[36m# ./spec/database_spec.rb:17:in `block (2 levels) in
'[0m
4) Combustion::Database returns test_another for model with
connection to second database
[31mFailure/Error:[0m
[31m expect(ModelInAnotherDb.connection_config[:database]).[0m
[31m to match(/test_another/)[0m
[31m[0m
[31mNoMethodError:[0m
[31m undefined method `expect' for
#[0m
[31m Did you mean? exec[0m
[36m# ./spec/database_spec.rb:28:in `block (2 levels) in
'[0m
Finished in 0.60768 seconds (files took 0.55044 seconds to load)
[31m4 examples, 4 failures[0m
--- End Message ---
--- Begin Message ---
Source: ruby-combustion
Source-Version: 1.1.1-3
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-combustion, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 956...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-combustion
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 23 Apr 2020 00:30:17 +0200
Source: ruby-combustion
Architecture: source
Version: 1.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
Changed-By: Daniel Leidert
Closes: 956598
Changes:
ruby-combustion (1.1.1-3) unstable; urgency=medium
.
* Team upload.
.
[ Debian Janitor ]
* Set field Upstream-Contact in debian/copyright.
* Remove obsolete fields Contact, Name from debian/upstream/metadata
(already present in machine-readable debian/copyright).
* Update standards version to 4.4.1, no changes needed.
.
[ Daniel Leidert ]
* d/clean: Add file and remove override in d/rules.
* d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.5.0.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/rules: Remove override_dh_clean target.
* d/watch: Minor update.
* d/patches/adjust-Gemfile.patch: Adjust.
- Add rspec to Gemfile to fix tests in autopkgtest (closes: #956598).
* d/upstream/metadata: Add Changelog fields and do minor updates.
Checksums-Sha1:
e3863233e4be8004050408a3628a19157ee68903 2182 ruby-combustion_1.1.1-3.dsc
473abe7fd4263d9e0b2e41c764947f3233e1c2ae 5588
ruby-combustion_1.1.1-3.debian.tar.xz
2dba25ab2c49ef3ddf3b2f98b45463694ca0f1be 12659
ruby-combustion_1.1.1-3_amd64.buildinfo
Checksums-Sha256:
017f8742591b6c26e25f8a4db2588732e7e395d17e4469be7e1d2bbd76aee0ac 2182
ruby-combustion_1.1.1-3.dsc
Bug#953537: Goffredo's patch
I'm curious if there's some problem with Goffredo's patch which hasn't been acknowledged. (In fact the bug itself hasn't been.) This is a grave functionality bug rendering the package uninstallable for all users upgrading from an installation of Buster. Certainly sid is sid, but as it required a NMU to fix this bug the first time four years ago and the package hasn't been touched since except to upload a new upstream without the patch. Has anyone heard from Nathan? Things are a little worrying in the outside world just now. Joseph
Bug#956598: marked as pending in ruby-combustion
Control: tag -1 pending Hello, Bug #956598 in ruby-combustion 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/ruby-team/ruby-combustion/-/commit/d9082b64d362c031151ca5dbeefb01bba9f4c234 Adjust patch to fix autopkgtest failure * d/patches/adjust-Gemfile.patch: Adjust. - Add rspec to Gemfile to fix tests in autopkgtest (closes: #956598). (this message was generated automatically) -- Greetings https://bugs.debian.org/956598
Processed: Bug#956598 marked as pending in ruby-combustion
Processing control commands: > tag -1 pending Bug #956598 [ruby-combustion] ruby-combustion autopkgtest is failing with NoMethodError: undefined method `expect' for # Added tag(s) pending. -- 956598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958496: python3-m2crypto: broken by Python3.8 - python3.8 http.client module expects that m2crypto handles short read
Package: python3-m2crypto Version: 0.31.0-9+b1 Severity: grave Justification: renders package unusable Dear maintainer, >From https://gitlab.com/m2crypto/m2crypto/-/merge_requests/242: In python3.8 the fp is wrapped in a Buffer. SSL.Connection.makefile returns a socketIO which is no buffer. SocketIO in 'r' mode: use io.BufferedReader SocketIO in 'rw' mode: use io.BufferedRWPair At the moment, m2crypto breaks down when chunked reads are done. See but report https://github.com/openSUSE/osc/issues/783 for more discussion. I attach a debdiff against the current package. I can confirm that the upstream fix applies cleanly to the version in Debian and fixes the problem. Thanks Norbert PS: m2crypto could need an update, too, latest version is 0.35.2 -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.5 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-m2crypto depends on: ii libc6 2.30-4 ii libssl1.1 1.1.1g-1 ii python33.8.2-3 python3-m2crypto recommends no packages. Versions of packages python3-m2crypto suggests: pn m2crypto-doc -- no debconf information diff -Nru m2crypto-0.31.0/debian/changelog m2crypto-0.31.0/debian/changelog --- m2crypto-0.31.0/debian/changelog2020-01-31 14:17:53.0 +0900 +++ m2crypto-0.31.0/debian/changelog2020-04-23 07:21:19.0 +0900 @@ -1,3 +1,13 @@ +m2crypto (0.31.0-9.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix incompatibility with Python 3.8 +python3.8 http.client module expects that m2crypto handles short read +(See https://github.com/openSUSE/osc/issues/783 and +https://github.com/openSUSE/osc/issues/783) + + -- Norbert Preining Thu, 23 Apr 2020 07:21:19 +0900 + m2crypto (0.31.0-9) unstable; urgency=medium [ Debian Janitor ] diff -Nru m2crypto-0.31.0/debian/patches/d3a43ffe1bfe4c128d6ab7c390419dee68f4ca5a.patch m2crypto-0.31.0/debian/patches/d3a43ffe1bfe4c128d6ab7c390419dee68f4ca5a.patch --- m2crypto-0.31.0/debian/patches/d3a43ffe1bfe4c128d6ab7c390419dee68f4ca5a.patch 1970-01-01 09:00:00.0 +0900 +++ m2crypto-0.31.0/debian/patches/d3a43ffe1bfe4c128d6ab7c390419dee68f4ca5a.patch 2020-04-23 07:15:49.0 +0900 @@ -0,0 +1,47 @@ +From d3a43ffe1bfe4c128d6ab7c390419dee68f4ca5a Mon Sep 17 00:00:00 2001 +From: lethliel +Date: Wed, 19 Feb 2020 11:53:05 +0100 +Subject: [PATCH] wrap SocketIO in io.Buffered* for makefile + +In python3.8 the fp is wrapped in a Buffer. +SSL.Connection.makefile returns a socketIO which is no buffer. + +SocketIO in 'r' mode: +use io.BufferedReader + +SocketIO in 'rw' mode: +use io.BufferedRWPair +--- + M2Crypto/SSL/Connection.py | 8 ++-- + 1 file changed, 6 insertions(+), 2 deletions(-) + +diff --git a/M2Crypto/SSL/Connection.py b/M2Crypto/SSL/Connection.py +index 7053aa6b..01bb61c5 100644 +--- a/M2Crypto/SSL/Connection.py b/M2Crypto/SSL/Connection.py +@@ -12,6 +12,7 @@ Copyright 2008 Heikki Toivonen. All rights reserved. + + import logging + import socket ++import io + + from M2Crypto import BIO, Err, X509, m2, py27plus, six, util # noqa + from M2Crypto.SSL import Checker, Context, timeout # noqa +@@ -582,9 +583,12 @@ class Connection(object): + return m2.ssl_set_cipher_list(self.ssl, cipher_list) + + def makefile(self, mode='rb', bufsize=-1): +-# type: (AnyStr, int) -> socket._fileobject ++# type: (AnyStr, int) -> Union[io.BufferedRWPair,io.BufferedReader] + if six.PY3: +-return socket.SocketIO(self, mode) ++raw = socket.SocketIO(self, mode) ++if 'rw' in mode: ++return io.BufferedRWPair(raw, raw) ++return io.BufferedReader(raw, io.DEFAULT_BUFFER_SIZE) + else: + return socket._fileobject(self, mode, bufsize) + +-- +2.26.2 + diff -Nru m2crypto-0.31.0/debian/patches/series m2crypto-0.31.0/debian/patches/series --- m2crypto-0.31.0/debian/patches/series 2020-01-31 14:17:53.0 +0900 +++ m2crypto-0.31.0/debian/patches/series 2020-04-23 07:18:47.0 +0900 @@ -4,3 +4,4 @@ 0004-Limit-tests.test_rsa.RSATestCase.test_public_encrypt.patch 0005-tests.test_rsa-Fix-typo-to-match-for-proper-exceptio.patch 0006-Be-resilient-against-the-situation-when-no-error-hap.patch +d3a43ffe1bfe4c128d6ab7c390419dee68f4ca5a.patch
Processed: closing 953689
Processing commands for cont...@bugs.debian.org: > close 953689 Bug #953689 [src:rust-enum-as-inner] src:rust-enum-as-inner: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 953690
Processing commands for cont...@bugs.debian.org:
> close 953690
Bug #953690 {Done: Ximin Luo } [src:rust-cpp-demangle]
src:rust-cpp-demangle: fails to migrate to testing for too long
Bug 953690 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
953690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 953179
Processing commands for cont...@bugs.debian.org: > close 953179 Bug #953179 [src:rust-glob] src:rust-glob: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953179 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 953688
Processing commands for cont...@bugs.debian.org: > close 953688 Bug #953688 [src:rust-tempfile] src:rust-tempfile: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 953690
Processing commands for cont...@bugs.debian.org: > close 953690 Bug #953690 [src:rust-cpp-demangle] src:rust-cpp-demangle: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: scilab: FTBFS: Scilab cannot create Scilab Java Main-Class (we have not been able to find the main Scilab class. Check if the Scilab and thirdparty packages are available).
Processing control commands: > tag -1 + patch Bug #955694 [src:scilab] scilab: FTBFS: Scilab cannot create Scilab Java Main-Class (we have not been able to find the main Scilab class. Check if the Scilab and thirdparty packages are available). Added tag(s) patch. -- 955694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955694: scilab: FTBFS: Scilab cannot create Scilab Java Main-Class (we have not been able to find the main Scilab class. Check if the Scilab and thirdparty packages are available).
Control: tag -1 + patch
Gilles Filippini a écrit le 22/04/2020 à 19:35 :
> Gilles Filippini a écrit le 22/04/2020 à 09:59 :
>> Hi,
>>
>> Matthias Klose a écrit le 20/04/2020 à 12:49 :
>>> On 4/20/20 11:52 AM, Gilles Filippini wrote:
I'd like to do a bisect between openjdk-11 11.0.6+10-2 and 11.0.7+9-1 to
better understand the problem but I can't find the corresponding branch
on the openjdk Mercurial repo.
>>>
>>> http://hg.openjdk.java.net/jdk-updates/jdk11u/
>>>
>>
>> This commit is the culprit:
>> http://hg.openjdk.java.net/jdk-updates/jdk11u/rev/21710e014d7f
>>
>> It makes sense since it is related to System.loadLibrary().
>>
>> Because Scilab loads Java from C++ code I guess moving usr_paths ans
>> sys_paths initialization out of System.loadLibrary might have some
>> consequences.
>>
>> Applying the attached patch to openjdk-11 solves the problem. Not sure
>> this is the right thing to do, but it keeps the deadlock fix brought by
>> the jdk changeset and allows for sys_paths and usr_paths initialization
>> in System.loadLibrary() when needed.
>>
>> @doko, please consider adding this patch to the openjdk-11 source
>> package until a proper fix is found for Scilab.
>
> I think I've eventually found a fix for Scilab. Please hold.
Here it is, attached.
_g.
diff -Nru scilab-6.1.0+dfsg1/debian/changelog
scilab-6.1.0+dfsg1/debian/changelog
--- scilab-6.1.0+dfsg1/debian/changelog 2020-03-01 17:03:05.0 +0100
+++ scilab-6.1.0+dfsg1/debian/changelog 2020-04-22 21:55:44.0 +0200
@@ -1,3 +1,11 @@
+scilab (6.1.0+dfsg1-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * New patch addLibraryPath.patch to fix NullPointerExeption with
+openjdk >= 11.0.7+9 (closes: #955694, #956908)
+
+ -- Gilles Filippini Wed, 22 Apr 2020 21:55:44 +0200
+
scilab (6.1.0+dfsg1-1) unstable; urgency=medium
* Package new upstream release 6.1.0.
diff -Nru scilab-6.1.0+dfsg1/debian/patches/addLibraryPath.patch
scilab-6.1.0+dfsg1/debian/patches/addLibraryPath.patch
--- scilab-6.1.0+dfsg1/debian/patches/addLibraryPath.patch 1970-01-01
01:00:00.0 +0100
+++ scilab-6.1.0+dfsg1/debian/patches/addLibraryPath.patch 2020-04-22
21:55:44.0 +0200
@@ -0,0 +1,40 @@
+Description: Starting with openjdk 11.0.7+9 it is not possible anymore
+ to force java.library.path reload by setting sys_paths to null.
+ Related jdk changeset:
+ http://hg.openjdk.java.net/jdk-updates/jdk11u/rev/21710e014d7f
+Author: Gilles Filippini
+Index:
scilab-6.1.0+dfsg1/scilab/modules/jvm/src/java/org/scilab/modules/jvm/LibraryPath.java
+===
+---
scilab-6.1.0+dfsg1.orig/scilab/modules/jvm/src/java/org/scilab/modules/jvm/LibraryPath.java
scilab-6.1.0+dfsg1/scilab/modules/jvm/src/java/org/scilab/modules/jvm/LibraryPath.java
+@@ -19,7 +19,8 @@ package org.scilab.modules.jvm;
+ /*--*/
+ import java.io.IOException;
+ import java.io.File;
+-import java.lang.reflect.Field;
++import java.lang.reflect.Method;
++import java.lang.reflect.InvocationTargetException;
+ /*--*/
+ /*http://forum.java.sun.com/thread.jspa?threadID=135560=15=0 */
+ /*--*/
+@@ -65,13 +66,13 @@ public class LibraryPath {
+ String newLibPath = System.getProperty(JAVALIBRARYPATH) +
File.pathSeparator + p;
+ System.setProperty(JAVALIBRARYPATH, newLibPath);
+ try {
+-Field fieldSysPath =
ClassLoader.class.getDeclaredField("sys_paths");
+-fieldSysPath.setAccessible(true);
+-if (fieldSysPath != null) {
+-fieldSysPath.set(System.class.getClassLoader(), null);
+-}
+-} catch (NoSuchFieldException e) {
+-throw new IOException("Error NoSuchFieldException, could not
add path to " + JAVALIBRARYPATH);
++final Method initLibraryPaths =
ClassLoader.class.getDeclaredMethod("initLibraryPaths");
++initLibraryPaths.setAccessible(true);
++initLibraryPaths.invoke(null);
++} catch (NoSuchMethodException e) {
++throw new IOException("Error NoSuchMethodException, could not
add path to " + JAVALIBRARYPATH);
++} catch (InvocationTargetException e) {
++throw new IOException("Error InvocationTargetException, could
not add path to " + JAVALIBRARYPATH);
+ } catch (IllegalAccessException e) {
+ throw new IOException("Error IllegalAccessException, could
not add path to " + JAVALIBRARYPATH);
+ }
diff -Nru scilab-6.1.0+dfsg1/debian/patches/series
scilab-6.1.0+dfsg1/debian/patches/series
--- scilab-6.1.0+dfsg1/debian/patches/series2020-03-01 17:03:05.0
+0100
+++
Bug#958495: gap-io: please update for new GAP ABI
Package: gap-io Version: 4.7.0+ds-1 Severity: serious Dear Debian Science Maintainers, Please update gap-io for the new GAP ABI. 1) GAP 4.11.0 includes libgap7, libgap-dev as a normal Debian shared library package. 2) There is now an officially supported ABI for the GAP kernel. the current kernel ABI version is 7 In the file /usr/lib/gap/sysinfo.gap GAParch=x86_64-pc-linux-gnu-default64-kv7 GAP_KERNEL_MAJOR_VERSION=7 kv7 mean kernel version 7. If your package is built against the GAP 4.11.0 kernel, please make it depends on gap-kernel-7. Cheers, -- Bill. Imagine a large red swirl here.
Bug#958430: closing 958430
close 958430 # error on user side, the libvirt box is fine. thanks
Bug#955078: marked as done (aodh: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info')
Your message dated Wed, 22 Apr 2020 23:19:52 +0200
with message-id <2d0a2ed9-985d-6802-db77-bf3d64125...@debian.org>
and subject line Issue was in sphinxcontrib-pecanwsme
has caused the Debian Bug report #955078,
regarding aodh: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no
attribute 'info'
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.)
--
955078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aodh
Version: 9.0.0-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4
Hi,
aodh fails to build with Sphinx 2.4, currently available in
experimental.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: Command not found
> py3versions: no X-Python3-Version in control file, using supported versions
> PYTHONPATH=. PYTHON=python3 python3 -m sphinx -b html doc/source
> /<>/debian/aodh-doc/usr/share/doc/aodh-doc/html
> Running Sphinx v2.4.3
> connecting events for openstackdocstheme
> /usr/lib/python3/dist-packages/wsmeext/sphinxext.py:162:
> RemovedInSphinx30Warning: sphinx.locale.l_() is deprecated. Please use `_()`
> instead.
> Field('datatype', label=l_('Type'), has_arg=False,
> /usr/lib/python3/dist-packages/wsmeext/sphinxext.py:553:
> RemovedInSphinx30Warning: sphinx.locale.l_() is deprecated. Please use `_()`
> instead.
> 'type': ObjType(l_('type'), 'type', 'obj'),
> /usr/lib/python3/dist-packages/wsmeext/sphinxext.py:554:
> RemovedInSphinx30Warning: sphinx.locale.l_() is deprecated. Please use `_()`
> instead.
> 'service': ObjType(l_('service'), 'service', 'obj')
>
> Exception occurred:
> File "/usr/lib/python3/dist-packages/sphinxcontrib/pecanwsme/rest.py", line
> 244, in setup
> app.info('Initializing %s' % __name__)
> AttributeError: 'Sphinx' object has no attribute 'info'
> The full traceback has been saved in /tmp/sphinx-err-s9yeez9d.log, if you
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error
> message can be provided next time.
> A bug report can be filed in the tracker at
> . Thanks!
> make[1]: *** [debian/rules:83: override_dh_sphinxdoc] Error 2
The full build log is available from:
http://qa-logs.debian.net/2020/03/26/aodh_9.0.0-2_unstable_sphinx243.log
Please see [1] for Sphinx changelog, which may give a hint of what changes in
Sphinx caused this error.
Also see [2] for the list of deprecated/removed APIs and possible alternatives
to them.
Sphinx 2.4 is going to be uploaded to unstable in a couple of weeks. When that
happens, the severity of this bug will be bumped to serious.
In case you have questions, please Cc sph...@packages.debian.org on reply.
[1]: https://www.sphinx-doc.org/en/2.0/changes.html
[2]:
https://www.sphinx-doc.org/en/2.0/extdev/deprecated.html#dev-deprecated-apis
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
This problem is fixed with sphinxcontrib-pecanwsme 0.10, and was never
in this package.
Thomas Goirand (zigo)--- End Message ---
Processed: closing 958430
Processing commands for cont...@bugs.debian.org: > close 958430 Bug #958430 [cloud.debian.org] Vagrant libvirt image debian/buster64 version 10.3.0 grub error Marked Bug as done > # error on user side, the libvirt box is fine. > thanks Stopping processing here. Please contact me if you need assistance. -- 958430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 958430
Processing commands for cont...@bugs.debian.org: > tags 958430 + unreproducible Bug #958430 [cloud.debian.org] Vagrant libvirt image debian/buster64 version 10.3.0 grub error Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 958430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958430: Vagrant libvirt
> Call to virDomainCreateWithFlags failed: internal error: process > exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 > Device or resource busy > 2020-04-22T19:06:13.421798Z qemu-system-x86_64: failed to initialize > KVM: Device or resource busy > And this fatal error in vb-buster when lv-buster is already started: > The guest machine entered an invalid state while waiting for it to > boot. Valid states are 'starting, running'. The machine is in the > 'gurumeditation' state. Yes, unfortunately VirtualBox and Libvirt with Qemu/Kvm cannot run at the same time. See https://github.com/canonical/multipass/issues/6#issuecomment-359802193 for details.
Bug#958493: sphinxcontrib-bibtex: autopkgtest regression
Source: sphinxcontrib-bibtex Version: 1.0.0-1 Severity: serious The autopkgtest of sphinxcontrib-bibtex fails, preventing its migration to testing. See https://ci.debian.net/data/autopkgtest/testing/amd64/s/sphinxcontrib-bibtex/5114485/log.gz Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#955084: marked as done (panko: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info')
Your message dated Wed, 22 Apr 2020 23:07:45 +0200
with message-id <585496d4-79d1-d5e0-746e-06738b5e4...@debian.org>
and subject line The issue was in python3-sphinxcontrib-pecanwsme
has caused the Debian Bug report #955084,
regarding panko: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no
attribute 'info'
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.)
--
955084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: panko
Version: 7.0.0-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4
Hi,
panko fails to build with Sphinx 2.4, currently available in
experimental.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: Command not found
> py3versions: no X-Python3-Version in control file, using supported versions
> python3 -m sphinx -b html doc/source
> /<>/debian/panko-doc/usr/share/doc/panko-doc/html
> Running Sphinx v2.4.3
>
> Exception occurred:
> File "/usr/lib/python3/dist-packages/sphinxcontrib/pecanwsme/rest.py", line
> 244, in setup
> app.info('Initializing %s' % __name__)
> AttributeError: 'Sphinx' object has no attribute 'info'
> The full traceback has been saved in /tmp/sphinx-err-czhha2_z.log, if you
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error
> message can be provided next time.
> A bug report can be filed in the tracker at
> . Thanks!
> make[1]: *** [debian/rules:68: override_dh_sphinxdoc] Error 2
The full build log is available from:
http://qa-logs.debian.net/2020/03/26/panko_7.0.0-2_unstable_sphinx243.log
Please see [1] for Sphinx changelog, which may give a hint of what changes in
Sphinx caused this error.
Also see [2] for the list of deprecated/removed APIs and possible alternatives
to them.
Sphinx 2.4 is going to be uploaded to unstable in a couple of weeks. When that
happens, the severity of this bug will be bumped to serious.
In case you have questions, please Cc sph...@packages.debian.org on reply.
[1]: https://www.sphinx-doc.org/en/2.0/changes.html
[2]:
https://www.sphinx-doc.org/en/2.0/extdev/deprecated.html#dev-deprecated-apis
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
The issue was in python3-sphinxcontrib-pecanwsme. Version 0.10.0-1 of it
fixed the problem.
Cheers,
Thomas Goirand (zigo)--- End Message ---
Bug#958492: xfonts-terminus: Provide gtk-compatible fonts
Package: xfonts-terminus Version: 4.40-2 Severity: grave Justification: renders package unusable Dear Maintainer, With pango 1.44, bitmap fonts are no longer supported: https://gitlab.gnome.org/GNOME/pango/issues/386 This means that trying to render Terminus in gtk applications looks like... well, this: https://rharwood.fedorapeople.org/screenshots/2020-04-22-162841_1920x1080_scrot.png The Fedora maintainer has adapted the terminus-fonts package to provide .otb files in more recent versions, using the approach described there and in https://bugzilla.redhat.com/show_bug.cgi?id=1753295 Thanks, --Robbie -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (700, 'testing-debug'), (700, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (300, 'experimental-debug'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-trunk-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=es_US.UTF-8, LC_CTYPE=es_US.UTF-8 (charmap=UTF-8), LANGUAGE=es_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xfonts-terminus depends on: ii xfonts-utils 1:7.7+6 xfonts-terminus recommends no packages. Versions of packages xfonts-terminus suggests: ii xfonts-terminus-oblique 4.40-2 ii xserver-xorg [xserver] 1:7.7+20 -- no debconf information
Bug#958491: acpica-unix: FTBFS on s390x
Source: acpica-unix Version: 20200326-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) acpica-unix failed to build on s390x: https://buildd.debian.org/status/fetch.php?pkg=acpica-unix=s390x=20200326-1=1585774833=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#958191: marked as done (dracut: processor microcode is not loaded (early cpio is not generated))
Your message dated Wed, 22 Apr 2020 20:34:07 + with message-id and subject line Bug#958191: fixed in dracut 050+35-3 has caused the Debian Bug report #958191, regarding dracut: processor microcode is not loaded (early cpio is not generated) 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.) -- 958191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dracut Version: 050+35-2 Severity: serious This newest version of dracut is not loading Intel microcode updates, and reverting to 048+80-2 resolves the issue. lsinitrd in 048 shows an early cpio archive with the microcode. that cpio is missing in 050, so maybe that is related? I've marked this serious because it can re-expose a system to spectre/meltdown bugs. Please adjust as you see fit. --- End Message --- --- Begin Message --- Source: dracut Source-Version: 050+35-3 Done: Thomas Lange We believe that the bug you reported is fixed in the latest version of dracut, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Lange (supplier of updated dracut 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: Wed, 22 Apr 2020 22:09:22 +0200 Source: dracut Architecture: source Version: 050+35-3 Distribution: unstable Urgency: high Maintainer: Thomas Lange Changed-By: Thomas Lange Closes: 958191 Changes: dracut (050+35-3) unstable; urgency=high . * fix microcode loading, Closes: #958191 Checksums-Sha1: 1927a115e144e82a919828b70cdced7eef9d5bf2 2330 dracut_050+35-3.dsc 748774a13ca1c4ae2440f7899629cee0fa612561 12704 dracut_050+35-3.debian.tar.xz fcc00b73d64a17c3f044316042e02636e05ebae5 8342 dracut_050+35-3_amd64.buildinfo Checksums-Sha256: 848635a35ae1d8f4b67c9b1f07544bee2a3b8119b5477bc7ed78ec98d5717edd 2330 dracut_050+35-3.dsc eb0fc04854680aa666f927b9a3e403456799deb69486b03b9848aa73b437ff21 12704 dracut_050+35-3.debian.tar.xz 32238ee21075bf63357223e03ec15e868f934790ec008acd2611094f5115f010 8342 dracut_050+35-3_amd64.buildinfo Files: 9a8284f5806fa6468d30dd84468f6681 2330 utils optional dracut_050+35-3.dsc d299cc53835ec4b3f2987a627977 12704 utils optional dracut_050+35-3.debian.tar.xz fbe3990d1a8f44d9a3b18d2a4b47d6b7 8342 utils optional dracut_050+35-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEsR7jJz9rLetSjJPaK/jZ/gdLzeQFAl6gpn8RHGxhbmdlQGRl Ymlhbi5vcmcACgkQK/jZ/gdLzeRSZQ/+KBH0V8FtZQ1vrLqGcUQ1r6tpd+nMDWno F4ZI2RQyYaprKCRLF+T+CbIRgpQwmgbT55mkRrM3nj6aVwVJOakjxEAOkKth7Zvl Ks9voZ2Xeod5/0FpwdagdXVtwCoaQsHh15jjMz/l/ZMvGFhIA8JC7HjYI0afANW/ c/dMDuzU07G7qhiUdfoM1sqpFgkzMegDkY5Om7IM7Asa9dCKrbvPzFXuY6eJu+90 or9RPwfzfQmTb7aBCCrlFEelI8dvURe21MeLpdQCoXyert8AQEvCAKemnM2pgl6b 9lmEq76gnCMey3IlqSkGR658S4V4O6yfzG2Xy05UFt2NbtlAF8aJ3xxwHes9azKv OkJTvu+fimYYdONGEcq9eiLFCRHZn3Iq7BIPj34hlHhe2iqVbpyWfQuCfexEFv6a ONI6tRWhnUtqmUDq+6uX1my2o+Qivh2pa1gpQfAtPrcDmsGVaVVl8QHaVCqwK6xz goOFR5P7zE8u+444Z2LQ2aEIFl4cXNtbSF82Y5MTjsgTNzctsBJUiYeIWWS1+tuo 6jPKfjwBwwH24XjJAZ0a1xcBdxCjfzk+DN/0V952LsjezhPJv4PaagZao8iToONK iHEi44IR7DvTSB0k1cWftooTi3rxi+fXaLEn9EoNwy7fBBrA7VCyrMmAG6SHKMDs E3awY8Tp07Q= =mVEc -END PGP SIGNATURE End Message ---
Bug#958471: marked as done (src:kineticstools: Non-free data included in source)
Your message dated Wed, 22 Apr 2020 20:35:11 + with message-id and subject line Bug#958471: fixed in kineticstools 0.6.1+git20200325.3558942+dfsg-1 has caused the Debian Bug report #958471, regarding src:kineticstools: Non-free data included in source 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.) -- 958471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kineticstools Version: 0.6.1+20161222-1 Severity: serious Justification: Policy 2.1 All versions of kineticstools in the archive include a non-free data file: doc/whitepaper/kinetics.tex The file includes the following statement: For Research Use Only. Not for use in diagnostic procedures. © Copyright 2012, Pacific Biosciences of California, Inc. All rights reserved. Information in this document is subject to change without notice. Pacific Biosciences assumes no responsibility for any errors or omissions in this document. Certain notices, terms, conditions and/or use restrictions may pertain to your use of Pacific Biosciences products and/or third party products. Please refer to the applicable Pacific Biosciences Terms and Conditions of Sale and to the applicable license terms at http://www.pacificbiosciences.com/licenses.html. The license on the linked page includes "non-exclusive, non-transferable, non-sublicensable license" and specifically mentions documentation, so this file is non-free and must be removed from the tarball. It's non-distributable, so it wouldn't even be suitable for non-free. Note that there are references in README.Source about repacking the tarball to remove non-free material that seem to be obsolete. Those should be updated when this is done. Scott K --- End Message --- --- Begin Message --- Source: kineticstools Source-Version: 0.6.1+git20200325.3558942+dfsg-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of kineticstools, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated kineticstools 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: Wed, 22 Apr 2020 22:14:02 +0200 Source: kineticstools Architecture: source Version: 0.6.1+git20200325.3558942+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 958471 Changes: kineticstools (0.6.1+git20200325.3558942+dfsg-1) unstable; urgency=medium . [ Etienne Mollier ] * minor d/rules update to make commands independent of minor python version . [ Andreas Tille ] * Remove non-free documentation from source tarball Closes: #958471 * Remove outdated README.source Checksums-Sha1: e5e3078d08bf48e45b79dcd36eec99a2e4a03e81 2690 kineticstools_0.6.1+git20200325.3558942+dfsg-1.dsc b92d64664aaed37aa408163ea081f9647bfb9060 21772336 kineticstools_0.6.1+git20200325.3558942+dfsg.orig.tar.xz 43e80128ee53c8d297ecb4183d8f73ec772fbf71 9904 kineticstools_0.6.1+git20200325.3558942+dfsg-1.debian.tar.xz c6a836bd12dca72f40089a27eb4a3a488a14b3ab 10247 kineticstools_0.6.1+git20200325.3558942+dfsg-1_amd64.buildinfo Checksums-Sha256: 709ce61a5ad549af75c7c3ebaf6633c9c387aebd6c498807b186e9464906db92 2690 kineticstools_0.6.1+git20200325.3558942+dfsg-1.dsc 8e5f583692085920ea3046512ade146e7a9c4ba3eb604da3ed982517b04e8a2c 21772336 kineticstools_0.6.1+git20200325.3558942+dfsg.orig.tar.xz bc56aae0d9fd85c49ea0148534c3179bcd536f525b9428df350503e134f37ae7 9904 kineticstools_0.6.1+git20200325.3558942+dfsg-1.debian.tar.xz 1ee6a93e1e31631eda0c8205ce9736fa4af46fbf072892f57e438a4638684d63 10247 kineticstools_0.6.1+git20200325.3558942+dfsg-1_amd64.buildinfo Files: 7cd7d1e92189e03a0460855c9e987df2 2690 science optional kineticstools_0.6.1+git20200325.3558942+dfsg-1.dsc 545d22f663e27e8c10c0a623c8b3f538 21772336 science optional kineticstools_0.6.1+git20200325.3558942+dfsg.orig.tar.xz 577e9a5183b3d8f791621481b9a1706e 9904 science optional kineticstools_0.6.1+git20200325.3558942+dfsg-1.debian.tar.xz
Processed: severity of 956672 is serious
Processing commands for cont...@bugs.debian.org: > severity 956672 serious Bug #956672 [rtkit] rtkit activation fails, because service unit is installed at the wrong place Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 956672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958430: Vagrant libvirt
Hi, Thanks for you reply. I already tried the mentioned commands before, but it did not see the hint up until now: Vagrant-libvirt plugin removed box only from you LOCAL ~/.vagrant/boxes directory >From libvirt storage pool you have to delete image manually(virsh, virt-manager or by any other tool) I also had the vagrant virtualbox image debian/buster64 version 10.3.0 in use, after deleting volume /var/lib/libvirt/images/debian-VAGRANTSLASH-buster64_vagrant_box_image_10.3.0.img from the default pool as hinted above everything seems to work, it was like the vagrant with libvirt provider was trying to start the virtualbox image somehow. Don't know how this happened I thought vagrant had native support for virtualbox and not through libvirt, but I see that I can't have both started at the same time (there are in different directories ~/lv-buster and ~/vb-buster), get this error in lv-buster when vb-buster is already started: Call to virDomainCreateWithFlags failed: internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy 2020-04-22T19:06:13.421798Z qemu-system-x86_64: failed to initialize KVM: Device or resource busy And this fatal error in vb-buster when lv-buster is already started: The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'gurumeditation' state. But this is probably a bug in vagrant itself? I'm new to vagrant my apologies for the incorrect bug report. Kind regards, Pascal
Bug#940215: Acknowledgement and Gratitude
Hi Bouyan Yang, Thanks a lot for taking care of this. I also appreciate the fact that you prepared a PR. It's merged now I'm happy with all the changes. Thank you for the upload. I don't know if it's possible but feel free to upload straight away if you want. Regards, -- Rock Storm GPG KeyID: 4096R/C96832FD GPG Fingerprint: C304 34B3 632C 464C 2FAF C741 0439 CF52 C968 32FD
Bug#956732: marked as done (gxr: Backends not packaged)
Your message dated Wed, 22 Apr 2020 18:00:12 + with message-id and subject line Bug#956732: fixed in gxr 0.14.0-3 has caused the Debian Bug report #956732, regarding gxr: Backends not packaged 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.) -- 956732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gxr Version: 0.14.0-2 Severity: grave Justification: renders package unusable Backends could be packaged in separate packages with the openvr backend in contrib somehow. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (980, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (120, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.5.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en_US (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: gxr Source-Version: 0.14.0-3 Done: =?utf-8?b?QW5kcmV3IExlZSAo5p2O5YGl56eLKQ==?= We believe that the bug you reported is fixed in the latest version of gxr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrew Lee (李健秋) (supplier of updated gxr 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, 21 Apr 2020 18:27:00 +0800 Source: gxr Binary: libgxr-0.14-0 libgxr-0.14-0-dbgsym libgxr-dev libgxr-openvr-0.14-0 libgxr-openvr-0.14-0-dbgsym libgxr-openxr-0.14-0 libgxr-openxr-0.14-0-dbgsym Architecture: source amd64 Version: 0.14.0-3 Distribution: unstable Urgency: medium Maintainer: Andrew Lee (李健秋) Changed-By: Andrew Lee (李健秋) Description: libgxr-0.14-0 - glib wrapper for OpenXR APIs libgxr-dev - glib wrapper for OpenVR and OpenXR APIs - development headers libgxr-openvr-0.14-0 - gxr backend for nonfree OpenVR libraries libgxr-openxr-0.14-0 - gxr backend for OpenXR libraries Closes: 956732 Changes: gxr (0.14.0-3) unstable; urgency=medium . * Update package descriptions. * Package both openvr and openxr backends. (Closes: #956732) * Use chrpath utility to remove the RPATH. Checksums-Sha1: 5f137c9ee6a39ed5feed4cc1283ebd7d62805af5 2311 gxr_0.14.0-3.dsc 890f6fafd44c30e80197ea842bb382f3e883760b 693298 gxr_0.14.0.orig.tar.bz2 5b46dce6ebebd6ed0dd398b08ed613dd25b19b9c 7280 gxr_0.14.0-3.debian.tar.xz b30425e72d885d1f0c766f473bc74733a5ab47b2 16559 gxr_0.14.0-3_amd64.buildinfo babb9c183107fcb3ecee141d09e5207930ef337d 67584 libgxr-0.14-0-dbgsym_0.14.0-3_amd64.deb a542801069afaabf7d6b61f8402dab45d0b4ec9d 20064 libgxr-0.14-0_0.14.0-3_amd64.deb a8a879373b2bb38e3c04a15434a46e566d837bc8 13692 libgxr-dev_0.14.0-3_amd64.deb 10d2d361aaa9f8baa02f3d29c62f1dcbd19c887a 226584 libgxr-openvr-0.14-0-dbgsym_0.14.0-3_amd64.deb 24edbb20923be32b05b2fe8f01fc2a41c887c5db 24284 libgxr-openvr-0.14-0_0.14.0-3_amd64.deb a2e4912cc9f6f243d1412034019ea7a484bedbce 75864 libgxr-openxr-0.14-0-dbgsym_0.14.0-3_amd64.deb e48340bacdc145657315b74ca2ed030173f32b9c 23056 libgxr-openxr-0.14-0_0.14.0-3_amd64.deb Checksums-Sha256: 34e2bc0c3bd9b28b917ce1bee48bffd3dc8c778cbbb10aa20fcbf8fcb6803154 2311 gxr_0.14.0-3.dsc 6eae063458ee00189ec9017cea07a8cde846c0fd762324bae45db312493c5e70 693298 gxr_0.14.0.orig.tar.bz2 15871634f74afdf633d4097136d9a6684e82e2cc7cf13636cea8f58df7d3fb49 7280 gxr_0.14.0-3.debian.tar.xz 35910c0ab971517d0cedecd843d858b8677a1278ce8d7a981b1117e9a88014fe 16559 gxr_0.14.0-3_amd64.buildinfo ace6c3e6330d92d2cd73e3ec0a11787189ee7653eb4c95738298d26129925cd1 67584 libgxr-0.14-0-dbgsym_0.14.0-3_amd64.deb 08244d59fdf678dbf98361adb09bb6f79b0c693ba07d8f1c2faeebaeb164c328 20064 libgxr-0.14-0_0.14.0-3_amd64.deb 35aa5872096ea4f98f6fd0e64b83cb66f13b2a06bf36a0940229b289c214636e 13692 libgxr-dev_0.14.0-3_amd64.deb
Bug#955694: scilab: FTBFS: Scilab cannot create Scilab Java Main-Class (we have not been able to find the main Scilab class. Check if the Scilab and thirdparty packages are available).
Gilles Filippini a écrit le 22/04/2020 à 09:59 : > Hi, > > Matthias Klose a écrit le 20/04/2020 à 12:49 : >> On 4/20/20 11:52 AM, Gilles Filippini wrote: >>> I'd like to do a bisect between openjdk-11 11.0.6+10-2 and 11.0.7+9-1 to >>> better understand the problem but I can't find the corresponding branch >>> on the openjdk Mercurial repo. >> >> http://hg.openjdk.java.net/jdk-updates/jdk11u/ >> > > This commit is the culprit: > http://hg.openjdk.java.net/jdk-updates/jdk11u/rev/21710e014d7f > > It makes sense since it is related to System.loadLibrary(). > > Because Scilab loads Java from C++ code I guess moving usr_paths ans > sys_paths initialization out of System.loadLibrary might have some > consequences. > > Applying the attached patch to openjdk-11 solves the problem. Not sure > this is the right thing to do, but it keeps the deadlock fix brought by > the jdk changeset and allows for sys_paths and usr_paths initialization > in System.loadLibrary() when needed. > > @doko, please consider adding this patch to the openjdk-11 source > package until a proper fix is found for Scilab. I think I've eventually found a fix for Scilab. Please hold. _g.
Bug#875584: Can jhdf be uploaded?
Hi, On Wed, Apr 22, 2020 at 06:32:55PM +0200, Giovanni Mascellani wrote: > Apparently jhdf has a patch committed in Salsa which would fix a FTBFS > (which currently prevents hdfview from installing in sid). Is there are > reason for not uploading it? Pretty please upload! Thank you Andreas. -- http://fam-tille.de
Bug#953694: marked as done (src:contextfree: fails to migrate to testing for too long)
Your message dated Wed, 22 Apr 2020 17:33:34 + with message-id and subject line Bug#953694: fixed in contextfree 3.3+dfsg1-1 has caused the Debian Bug report #953694, regarding src:contextfree: fails to migrate to testing for too long to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 953694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: contextfree Version: 3.1+dfsg1-2 Severity: serious Control: fixed -1 3.2+dfsg1-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:contextfree in its current version in unstable has been trying to migrate for 166 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=contextfree signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: contextfree Source-Version: 3.3+dfsg1-1 Done: John Horigan We believe that the bug you reported is fixed in the latest version of contextfree, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 953...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. John Horigan (supplier of updated contextfree package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Mar 2020 12:44:17 -0700 Source: contextfree Architecture: source Version: 3.3+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: John Horigan Changed-By: John Horigan Closes: 950882 951939 953694 Changes: contextfree (3.3+dfsg1-1) unstable; urgency=medium . * New upstream release * Adds missing includes (Closes: #951939) * Uploaded package is source-only (Closes: #950882) (Closes: #953694) * Updated Standards-Version to 4.5.0 (no changes) * Enable optional QuickTime/FFmpeg support. Checksums-Sha1: 170673f272fe8892d1a3a1b5a7d68d48fb79af11 2131 contextfree_3.3+dfsg1-1.dsc 6d35a092416a2433e9ef75be385a5d6302cff289 431620 contextfree_3.3+dfsg1.orig.tar.xz 842b5a1b03b8a17f614425b83c40c1527a4129c6 8600 contextfree_3.3+dfsg1-1.debian.tar.xz a9f537b2867862ff134e03c64a2909492f250983 9379 contextfree_3.3+dfsg1-1_amd64.buildinfo Checksums-Sha256: 4a712b881155aead280d20236f5be2b52cd3b1ade944d2e6d9944bd36b58aafd 2131 contextfree_3.3+dfsg1-1.dsc df9257beb0c502c641dbab4975ffae3e7fb7eaa37a445fef086e4b43e66e18b4 431620 contextfree_3.3+dfsg1.orig.tar.xz 6ccbc181c2e7f7b83bfec84bb9f9d477b81faffb40a4c72c30b5d0f7c354c4b7 8600 contextfree_3.3+dfsg1-1.debian.tar.xz 5414d8fb67370973f4141f29de4b18c261fb355914ca9fb5a930d951a0c7bf28 9379 contextfree_3.3+dfsg1-1_amd64.buildinfo Files: 3c0ab5643fbfd1eb371ad8d1a11021a9 2131 graphics optional contextfree_3.3+dfsg1-1.dsc b5bfee538fa7abf5af99bf9b7c802220 431620 graphics optional contextfree_3.3+dfsg1.orig.tar.xz 6223a3be72066a60720cb75e3cf84d88 8600 graphics optional
Bug#951939: marked as done (contextfree: FTBFS: src-common/cfdg.cpp:75:71: error: no matching function for call to ‘find(std::array, 18>::const_iterator, std::array
Your message dated Wed, 22 Apr 2020 17:33:34 +
with message-id
and subject line Bug#951939: fixed in contextfree 3.3+dfsg1-1
has caused the Debian Bug report #951939,
regarding contextfree: FTBFS: src-common/cfdg.cpp:75:71: error: no matching
function for call to ‘find(std::array,
18>::const_iterator, std::array,
18>::const_iterator, const string&)’
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.)
--
951939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: contextfree
Version: 3.2+dfsg1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Isrc-common -Isrc-unix -Iobjs
> -Isrc-common/agg-extras -Isrc-ffmpeg/include -I/usr/local/include -O2 -Wall
> -Wextra -Wno-parentheses -std=c++14 -g -D_GLIBCXX_USE_C99_MATH=1 -Wdate-time
> -D_FORTIFY_SOURCE=2 -DNDEBUG -c -o objs/cfdgimpl.o src-common/cfdgimpl.cpp
> src-common/cfdg.cpp: In static member function ‘static CFG
> CFDG::lookupCfg(const string&)’:
> src-common/cfdg.cpp:75:71: error: no matching function for call to
> ‘find(std::array, 18>::const_iterator,
> std::array, 18>::const_iterator, const
> string&)’
>75 | auto nameIt = std::find(ParamNames.begin(), ParamNames.end(),
> name);
> |
> ^
> In file included from /usr/include/c++/9/bits/locale_facets.h:48,
> from /usr/include/c++/9/bits/basic_ios.h:37,
> from /usr/include/c++/9/ios:44,
> from /usr/include/c++/9/ostream:38,
> from /usr/include/c++/9/iostream:39,
> from objs/location.hh:41,
> from src-common/cfdg.h:40,
> from src-common/cfdg.cpp:31:
> /usr/include/c++/9/bits/streambuf_iterator.h:373:5: note: candidate:
> ‘template typename
> __gnu_cxx::__enable_if::__value,
> std::istreambuf_iterator<_CharT> >::__type
> std::find(std::istreambuf_iterator<_CharT>, std::istreambuf_iterator<_CharT>,
> const _CharT2&)’
> 373 | find(istreambuf_iterator<_CharT> __first,
> | ^~~~
> /usr/include/c++/9/bits/streambuf_iterator.h:373:5: note: template argument
> deduction/substitution failed:
> src-common/cfdg.cpp:75:71: note: mismatched types
> ‘std::istreambuf_iterator<_CharT>’ and ‘const value_type*’ {aka ‘const
> std::__cxx11::basic_string*’}
>75 | auto nameIt = std::find(ParamNames.begin(), ParamNames.end(),
> name);
> |
> ^
> g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Isrc-common -Isrc-unix -Iobjs
> -Isrc-common/agg-extras -Isrc-ffmpeg/include -I/usr/local/include -O2 -Wall
> -Wextra -Wno-parentheses -std=c++14 -g -D_GLIBCXX_USE_C99_MATH=1 -Wdate-time
> -D_FORTIFY_SOURCE=2 -DNDEBUG -c -o objs/renderimpl.o
> src-common/renderimpl.cpp
> make[1]: *** [Makefile:207: objs/cfdg.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/contextfree_3.2+dfsg1-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: contextfree
Source-Version: 3.3+dfsg1-1
Done: John Horigan
We believe that the bug you reported is fixed in the latest version of
contextfree, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 951...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
John Horigan (supplier of updated contextfree 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
Bug#875584: Can jhdf be uploaded?
Apparently jhdf has a patch committed in Salsa which would fix a FTBFS (which currently prevents hdfview from installing in sid). Is there are reason for not uploading it? Thanks, Giovanni. -- Giovanni Mascellani Postdoc researcher - Université Libre de Bruxelles signature.asc Description: OpenPGP digital signature
Bug#954227: marked as done (node-eslint-plugin-node: unsuitable for stable release: too broken)
Your message dated Wed, 22 Apr 2020 16:04:08 + with message-id and subject line Bug#954227: fixed in node-eslint-plugin-node 8.0.1~ds-3 has caused the Debian Bug report #954227, regarding node-eslint-plugin-node: unsuitable for stable release: too broken 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.) -- 954227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-eslint-plugin-node Version: 6.0.1~dfsg-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Two rules (out of 13 rules in total) are broken: no-missing-import no-missing-require The breakage is (at least partly) caused by an uncoordinated release of too new node-espree. For now, the two broken rules have been dropped from "recommended" list, making the package suitable for _some_ test purposes, but *unsuitable* for stable release. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl5ygRcACgkQLHwxRsGg ASFhgg//T0JFnPSBOSst+lNVUFa+jLtba6OfSUpR21Aa2d9W2PfptVQEn9T7zi8D 7AqBU3+V7c0z4OA6NjFXzs+otmjHCWC0mYKBLQQLUCUZPP1p2wFzUSR8i4lEoFEc rn00ug/1/iUdtICc2dVcuU8jIC5em0H7DAodE7hDbxBy+rYHZvDFii7smOhM+/Ct GAcNTMmuAuN8LpMC9DqAP0sn2Sn+ICgEU+v01a6YKRZKBCnGtTJovwu9dApkdP83 0bx6OaR9g7CgSjgPZzoy4uggPidaWMeOEQeGV+JHumrWmeSXESIqEn8mLmbWQPQD +xK66Ippl/YUiBUjCBurCeKprr7IiiM7JaRbWqfa8ICARJj5wO5O9Xny4BlUTdhw QA9PZVs/ivS5eFdIXHvU+TnseHHH+fvwXpwvMxeVjSdzjyWgZwgL7CphlY1tVBqr OgDQ6kFNTOlbNKd8N6/OPWLsknvCmHNHZLkzuBnW5xH9fgsv5iuVv0P45tQ6KYUQ 06Me8lU23+v5zK0PkRUd19CkpRzLFEoh/XB7XKRady8XTBms3JYRyuO7nyeE/e1x I0llynFc/0Yq/5Gcstq5HPutC51lSti4DXQkbU2cFcyHW3l3oLmzZv9s1oCrEIpV +9g5+q5GIfOAGkL3nTwDkRzP85DJm0bu+f0Xa35MivZ/xPLKuro= =iXdm -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: node-eslint-plugin-node Source-Version: 8.0.1~ds-3 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of node-eslint-plugin-node, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated node-eslint-plugin-node package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 22 Apr 2020 17:35:46 +0200 Source: node-eslint-plugin-node Architecture: source Version: 8.0.1~ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Closes: 954227 Changes: node-eslint-plugin-node (8.0.1~ds-3) unstable; urgency=medium . * add patch 1001 to use system modules as default resolved paths * re-enable rules no-missing-import no-missing-require; closes: bug#954227 * fix helper script tap-todo counting, and emit error message on failure Checksums-Sha1: 954bf21eb71c28f9450f05d87ebfecbd80089bd8 2381 node-eslint-plugin-node_8.0.1~ds-3.dsc eb7926892779db80f3e0585f5137875d89e6c0cd 7940 node-eslint-plugin-node_8.0.1~ds-3.debian.tar.xz fbe9daa60bab487ad88899f595cf8c4377f90dcc 11205 node-eslint-plugin-node_8.0.1~ds-3_amd64.buildinfo Checksums-Sha256: 8b7cf7150ea6fbf73936365b93526f87cf937afcd97842719bdd377488c3a7a1 2381 node-eslint-plugin-node_8.0.1~ds-3.dsc 9adb57c33c473cdb5f67a784eb3dcf8ba6da060c6aeba44f2b9c40add7c70d64 7940 node-eslint-plugin-node_8.0.1~ds-3.debian.tar.xz 6e40daab8da50256b3a591f11972336213f568cd1db6fb53d933cd669c5670a6 11205 node-eslint-plugin-node_8.0.1~ds-3_amd64.buildinfo Files: ca4e01acff974cdfde369cc4699d5896 2381 javascript optional node-eslint-plugin-node_8.0.1~ds-3.dsc 89387057b33dc22cd3d7a5fa79a12de4 7940 javascript optional node-eslint-plugin-node_8.0.1~ds-3.debian.tar.xz 2c5c9e7d6a3e19a848ec73fb72cf9d97 11205 javascript optional node-eslint-plugin-node_8.0.1~ds-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl6gZtEACgkQLHwxRsGg ASGhOQ/8DoOUdUvsniwB01DKWzIU6A6Ttfwkmw++fCplLOCD4wAWtHluXRt3hz/A ENOKUQwM4YvxA9HAKNAP8PIIHzpn+n84QV2LR9QHVKgl+/QKjWH6/JnVZKl/zIl8 l6oGKjKUODR+nduQIPxb0+wrV2Vs8KwkCgR/4KKlu5eg2+ipJSFoixvKISg0Kv5E
Bug#936797: marked as done (kineticstools: Python2 removal in sid/bullseye)
Your message dated Wed, 22 Apr 2020 16:00:09 + with message-id and subject line Bug#936797: fixed in kineticstools 0.6.1+git20200325.3558942-1 has caused the Debian Bug report #936797, regarding kineticstools: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kineticstools Version: 0.6.1+git20180425.27a1878-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:kineticstools If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: kineticstools Source-Version: 0.6.1+git20200325.3558942-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of kineticstools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated kineticstools 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, 21 Apr 2020 11:12:01 +0200 Source: kineticstools Binary: kineticstools kineticstools-data python3-kineticstools python3-kineticstools-dbgsym Architecture: source all amd64 Version: 0.6.1+git20200325.3558942-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: kineticstools - detection of DNA modifications kineticstools-data - detection of DNA modifications -- data files python3-kineticstools - detection of DNA modifications (Python 2 library) Closes: 936797 Changes: kineticstools (0.6.1+git20200325.3558942-1) unstable; urgency=medium . [ Steffen Moeller ] * New upstream version * d/control - Standards-Version: 4.5.0 (routine-update) - debhelper-compat 12 (routine-update) - python3-uritools added as build dependency - added flags -
Processed: printrun: diff for NMU version 2.0.0~rc5-1.1
Processing control commands: > tags -1 +patch +pending Bug #940215 [src:printrun] printrun: missing Breaks+Replaces: printrun (<< 2) for package split Added tag(s) patch. Bug #940215 [src:printrun] printrun: missing Breaks+Replaces: printrun (<< 2) for package split Ignoring request to alter tags of bug #940215 to the same tags previously set -- 940215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: printrun: diff for NMU version 2.0.0~rc5-1.1
Processing control commands: > tags -1 +patch +pending Bug #956842 [src:printrun] printrun: FTBFS with python 3.8 Ignoring request to alter tags of bug #956842 to the same tags previously set Bug #956842 [src:printrun] printrun: FTBFS with python 3.8 Added tag(s) pending. -- 956842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#940215: printrun: diff for NMU version 2.0.0~rc5-1.1
Control: tags -1 +patch +pending
X-Debbugs-CC: rockst...@gmx.com
Dear maintainer,
I've prepared an NMU for printrun (versioned as 2.0.0~rc5-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Let me know asap if you have any questions or issues.
Regards,
Boyuan Yang
diff -Nru printrun-2.0.0~rc5/debian/changelog printrun-
2.0.0~rc5/debian/changelog
--- printrun-2.0.0~rc5/debian/changelog 2019-08-16 13:24:46.0 -0400
+++ printrun-2.0.0~rc5/debian/changelog 2020-04-22 11:38:15.0 -0400
@@ -1,3 +1,18 @@
+printrun (2.0.0~rc5-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Sven Bartscher ]
+ * Add breaks+replaces on printrun (<< 2)
+(Closes: #940215)
+
+ [ Boyuan Yang ]
+ * debian/rules: Force removal of .so files so we don't fail on arch:any
+(Closes: #956842)
+ * Source-only upload to allow testing migration.
+
+ -- Boyuan Yang Wed, 22 Apr 2020 11:38:15 -0400
+
printrun (2.0.0~rc5-1) unstable; urgency=low
* [662bb8f] New upstream version 2.0.0~rc5
diff -Nru printrun-2.0.0~rc5/debian/control printrun-2.0.0~rc5/debian/control
--- printrun-2.0.0~rc5/debian/control 2019-08-16 13:24:46.0 -0400
+++ printrun-2.0.0~rc5/debian/control 2020-04-22 11:32:17.0 -0400
@@ -40,6 +40,8 @@
${misc:Depends},
${python3:Depends},
${shlibs:Depends},
+Breaks: printrun (<< 2)
+Replaces: printrun (<< 2)
Description: 3D printer host core commands
Printrun is a full suite of host interfaces for 3D printers and CNC,
consisting of:
@@ -60,6 +62,8 @@
${misc:Depends},
${python3:Depends},
Recommends: slic3r,
+Breaks: printrun (<< 2)
+Replaces: printrun (<< 2)
Description: Command-line 3D printer host
Printrun is a full suite of host interfaces for 3D printers and CNC,
consisting of:
@@ -85,6 +89,8 @@
${misc:Depends},
${python3:Depends},
Recommends: slic3r,
+Breaks: printrun (<< 2)
+Replaces: printrun (<< 2)
Description: Graphical 3D printer host
Printrun is a full suite of host interfaces for 3D printers and CNC,
consisting of:
@@ -107,6 +113,8 @@
python3-wxgtk4.0,
${misc:Depends},
${python3:Depends},
+Breaks: printrun (<< 2)
+Replaces: printrun (<< 2)
Description: Graphical tool to prepare 3D printing plates
Printrun is a full suite of host interfaces for 3D printers and CNC,
consisting of:
diff -Nru printrun-2.0.0~rc5/debian/rules printrun-2.0.0~rc5/debian/rules
--- printrun-2.0.0~rc5/debian/rules 2019-08-16 13:24:46.0 -0400
+++ printrun-2.0.0~rc5/debian/rules 2020-04-22 11:36:18.0 -0400
@@ -18,7 +18,7 @@
override_dh_install:
dh_install --exclude='.pyc'
# Move arch-dependent library from printrun-common
- rm debian/printrun-common/usr/lib/python*/dist-packages/printrun/*.so
+ rm -f debian/printrun-common/usr/lib/python*/dist-
packages/printrun/*.so
override_dh_installchangelogs:
dh_installchangelogs NEWS.md
signature.asc
Description: This is a digitally signed message part
Bug#958471: src:kineticstools: Non-free data included in source
Package: src:kineticstools Version: 0.6.1+20161222-1 Severity: serious Justification: Policy 2.1 All versions of kineticstools in the archive include a non-free data file: doc/whitepaper/kinetics.tex The file includes the following statement: For Research Use Only. Not for use in diagnostic procedures. © Copyright 2012, Pacific Biosciences of California, Inc. All rights reserved. Information in this document is subject to change without notice. Pacific Biosciences assumes no responsibility for any errors or omissions in this document. Certain notices, terms, conditions and/or use restrictions may pertain to your use of Pacific Biosciences products and/or third party products. Please refer to the applicable Pacific Biosciences Terms and Conditions of Sale and to the applicable license terms at http://www.pacificbiosciences.com/licenses.html. The license on the linked page includes "non-exclusive, non-transferable, non-sublicensable license" and specifically mentions documentation, so this file is non-free and must be removed from the tarball. It's non-distributable, so it wouldn't even be suitable for non-free. Note that there are references in README.Source about repacking the tarball to remove non-free material that seem to be obsolete. Those should be updated when this is done. Scott K
Processed: Add missing sources
Processing commands for cont...@bugs.debian.org: > tags 787599 patch Bug #787599 [ganglia-web] Some sources are not included in your package Added tag(s) patch. > thank you Stopping processing here. Please contact me if you need assistance. -- 787599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947089: marked as done (uftrace: blocked migration to testing: autopkgtest times out on arm64 and FTBFS on armhf)
Your message dated Wed, 22 Apr 2020 14:35:21 + with message-id and subject line Bug#947089: fixed in uftrace 0.9.4-0.2 has caused the Debian Bug report #947089, regarding uftrace: blocked migration to testing: autopkgtest times out on arm64 and FTBFS on armhf 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.) -- 947089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uftrace Version: 0.9.3-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious Tags: ftbfs User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of uftrace you added an autopkgtest to uftrace, great. However, it fails due to timeout on arm64. Currently this failure is blocking the migration to testing [1]. Additionally the package fails to armhf [2]. The amd64 binary upload can be fixed by a binNMU, but we prefer source only uploads nowadays. Can you please investigate the situation and fix the arm64 autopkgtest timeout and armhf ftbfs? Paul [1] https://qa.debian.org/excuses.php?package=uftrace [2] Tail of log for uftrace on armhf: gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<> -iquote /<>/arch/arm -W -Wall -Wno-unused-parameter -Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW -DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW -DHAVE_LIBCAPSTONE -I/usr/include/capstone -fPIC -fvisibility=hidden -fno-omit-frame-pointer -c -o /<>/libmcount/symbol-libelf.op /<>/utils/symbol-libelf.c gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<> -iquote /<>/arch/arm -W -Wall -Wno-unused-parameter -Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW -DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW -DHAVE_LIBCAPSTONE -I/usr/include/capstone -fPIC -fvisibility=hidden -fno-omit-frame-pointer -c -o /<>/libmcount/symbol.op /<>/utils/symbol.c gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<> -iquote /<>/arch/arm -W -Wall -Wno-unused-parameter -Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW -DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW -DHAVE_LIBCAPSTONE -I/usr/include/capstone -fPIC -fvisibility=hidden -fno-omit-frame-pointer -c -o /<>/arch/arm/mcount.op /<>/arch/arm/mcount.S gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<> -iquote /<>/arch/arm -W -Wall -Wno-unused-parameter -Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW -DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW -DHAVE_LIBCAPSTONE -I/usr/include/capstone -fPIC -fvisibility=hidden -fno-omit-frame-pointer -c -o /<>/arch/arm/plthook.op /<>/arch/arm/plthook.S gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<> -iquote /<>/arch/arm -W -Wall -Wno-unused-parameter -Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW -DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW -DHAVE_LIBCAPSTONE -I/usr/include/capstone -fPIC -fvisibility=hidden -fno-omit-frame-pointer -c -o /<>/arch/arm/mcount-support.op /<>/arch/arm/mcount-support.c /<>/arch/arm/mcount-support.c: In function ‘mcount_arch_parent_location’: /<>/arch/arm/mcount-support.c:289:2: error: ‘cache’ undeclared (first use in this function) 289 | cache = lookup_cache(_cache, sym->addr, true); | ^ /<>/arch/arm/mcount-support.c:289:2: note: each undeclared identifier is reported only once for each function it appears in make[2]: *** [Makefile:28: /<>/arch/arm/mcount-support.op] Error 1 make[1]: *** [Makefile:242: /<>/arch/arm/mcount-entry.op] Error 2 make[1]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 make: *** [debian/rules:14: binary-arch] Error 255 signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: uftrace Source-Version: 0.9.4-0.2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version
Bug#796536: criu: package not yet ready for stable release / fast moving (blocking bug)
On Sat, Aug 22, 2015 at 02:24:48PM +0200, Salvatore Bonaccorso wrote: > Source: criu > Version: 1.6-2 > Severity: serious > > I'm filling this bug as blocking bug for criu for testing. Criu is by > now still a fast moving project and at this point it is not yet ready > to be effectively used in a stable release. For documentation purposes adding the following: I got contacted by the LXC maintainers, specifically due to potentially enabling the lxc-checkpoint tool, but only if we lift this blocking bug and allow criu to be released in bullseye. This is a valid request, and will look into if #796536 is still too overcautious and we should actually move on and include criu in the next stable release. Salvatore
Bug#947089: uftrace: diff for NMU version 0.9.4-0.2
Dear maintainer, I've prepared an NMU for uftrace (versioned as 0.9.4-0.2) and uploaded it. cu Adrian diff -Nru uftrace-0.9.4/debian/changelog uftrace-0.9.4/debian/changelog --- uftrace-0.9.4/debian/changelog 2020-04-13 16:18:27.0 +0300 +++ uftrace-0.9.4/debian/changelog 2020-04-22 17:06:49.0 +0300 @@ -1,3 +1,11 @@ +uftrace (0.9.4-0.2) unstable; urgency=high + + * Non-maintainer upload. + * Remove the autopkgtest for now, it doesn't fail when tests fail +but fails for other reasons on arm64. (Closes: #947089) + + -- Adrian Bunk Wed, 22 Apr 2020 17:06:49 +0300 + uftrace (0.9.4-0.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru uftrace-0.9.4/debian/tests/control uftrace-0.9.4/debian/tests/control --- uftrace-0.9.4/debian/tests/control 2019-09-19 05:14:16.0 +0300 +++ uftrace-0.9.4/debian/tests/control 1970-01-01 02:00:00.0 +0200 @@ -1,3 +0,0 @@ -Test-Command: cd tests && objdir=/usr/bin python runtest.py -Depends: @, build-essential, python -Restrictions: allow-stderr
Bug#937144: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).
On 4/22/20 6:23 AM, Valentin Vidić wrote: > On Tue, Apr 21, 2020 at 11:20:16PM +0200, Thomas Goirand wrote: >> You can remove all of the python-oslo* from the list. The versions in >> Experimental, which are the next version of OpenStack, are fixed. In 2 >> weeks of time, I'll upload all what I staged in Experimental to Sid >> (maybe 150 packages?) and that's going to fix it all. > > Will the new OpenStack version also fix this issue? > > #955116 python-murano-pkg-check: FTBFS with Sphinx 2.4: AttributeError: > 'Sphinx' object has no attribute 'info' Hopefully yes. As I understand, the issue is in oslo-sphinx, which is deprecated. I checked, and the master branch of murano-pkg-check doesn't use oslo-sphinx (and is therefore fixed). I'm waiting for it to be released, hopefully this week or the next one. Cheers, Thomas Goirand (zigo)
Bug#942988: displaycal: Python2 removal in sid/bullseye
On Wed, 22 Apr 2020, Christian Marillat wrote: On 17 avril 2020 11:32, Scott Talbert wrote: [...] It looks like upstream doesn't seem to be making much progress on this. Do you think that we need to start working on Python 3 support ourselves? Duplicate work is a bad idea. Otherwise upstream is still active in displaycal forums (18/04/2020) : https://hub.displaycal.net/forums/topic/battery-life/ It wouldn't be duplicative work. It could be provided to upstream. There doesn't appear to be any upstream commits since 2020-01-14... Scott
Processed: retitle 958191
Processing commands for cont...@bugs.debian.org: > retitle 958191 dracut: processor microcode is not loaded (early cpio is not > generated) Bug #958191 [dracut] processor microcode is not loaded (not dracut: early cpio is not produced) Changed Bug title to 'dracut: processor microcode is not loaded (early cpio is not generated)' from 'processor microcode is not loaded (not dracut: early cpio is not produced)'. > End of message, stopping processing here. Please contact me if you need assistance. -- 958191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 958180 in roundcube/1.4.3+dfsg.1-1~bpo10+1
Processing commands for cont...@bugs.debian.org:
> notfound 958180 roundcube/1.4.3+dfsg.1-1~bpo10+1
Bug #958180 {Done: Guilhem Moulin } [roundcube-core]
roundcube: roundcube cannot be installed from the backport
No longer marked as found in versions roundcube/1.4.3+dfsg.1-1~bpo10+1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
958180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#958180: marked as done (roundcube: roundcube cannot be installed from the backport)
Your message dated Wed, 22 Apr 2020 13:46:56 +0200 with message-id <20200422114656.ga1015...@debian.org> and subject line Re: [Pkg-roundcube-maintainers] Bug#958180: roundcube: roundcube cannot be installed from the backport has caused the Debian Bug report #958180, regarding roundcube: roundcube cannot be installed from the backport 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.) -- 958180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: roundcube-core Version: 1.3.10+dfsg.1-1~deb10u1 Severity: normal File: roundcube Dear Maintainer, The roundcube package is now also in the backports. As a result, my previous version was uninstalled and the current version from the backports cannot be installed. roundcube-core: Depends on: php-masterminds-html5 (> = 2.5.0) but cannot be installed -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-0.bpo.4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages roundcube-core depends on: ii dbconfig-common 2.0.11+deb10u1 ii debconf [debconf-2.0] 1.5.71 ii dpkg1.19.7 ii libmagic1 1:5.35-4+deb10u1 ii php 2:7.3+69 pn php-auth-sasl ii php-common 2:69 pn php-intl pn php-mail-mime pn php-net-sieve pn php-net-smtp pn php-net-socket ii php-pear1:1.10.6+submodules+notgz-1.1 ii php7.3 [php]7.3.14-1~deb10u1 ii php7.3-cli [php-cli]7.3.14-1~deb10u1 ii php7.3-json [php-json] 7.3.14-1~deb10u1 ii roundcube-mysql 1.4.3+dfsg.1-1~bpo10+1 ii ucf 3.0038+nmu1 Versions of packages roundcube-core recommends: ii apache2 [httpd-cgi] 2.4.41-1~bpo10+1 ii php-gd2:7.3+69 pn php-pspell ii php7.3-fpm [php-fpm] 7.3.14-1~deb10u1 ii php7.3-gd [php-gd]7.3.14-1~deb10u1 Versions of packages roundcube-core suggests: pn php-crypt-gpg pn php-net-ldap2 pn php-net-ldap3 pn roundcube-plugins -- Configuration Files: /etc/roundcube/apache.conf changed [not included] --- End Message --- --- Begin Message --- > roundcube-core: Depends on: php-masterminds-html5 (> = 2.5.0) but cannot be > installed Uploaded php-masterminds-html5 2.7.0+dfsg-3~bpo10+1 to buster-backports: https://tracker.debian.org/news/1120942/accepted-php-masterminds-html5-270dfsg-3bpo101-source-all-into-buster-backports-buster-backports/ -- Guilhem. signature.asc Description: PGP signature --- End Message ---
Bug#958460: FTBFS with no network
Package: appstream-generator Version: 0.8.1-1 Severity: serious This is a policy violation, as the build process must not rely on network accessibility. Error message: [139/147] /usr/bin/xsltproc --nonet --stringparam man.output.quietly 1 --stringparam funcsynopsis.style ansi --stringparam man.th.extra1.suppress 1 -o docs/appstream-generator.1 http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl ../docs/appstream-generator.1.xml I/O error : Attempt to load network entity http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd ../docs/appstream-generator.1.xml:12: warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd; ]> ^ While the message above is supposed to only be a warning, this reproducibly leads to a test timeout (30.01s). So either the timeout needs to be fixed or this specific test changed to no try to download the entity or this specific test needs to be disabled. Cheers, Sven
Processed: Re: Bug#955715 closed by Alastair McKinstry (FIxed in toolchain)
Processing control commands:
> notfound -1 adios/1.13.1-21
Bug #955715 {Done: Alastair McKinstry } [src:adios]
adios: FTBFS (error: could not find mpi library for Fortran)
No longer marked as found in versions adios/1.13.1-21.
> severity -1 normal
Bug #955715 {Done: Alastair McKinstry } [src:adios]
adios: FTBFS (error: could not find mpi library for Fortran)
Severity set to 'normal' from 'serious'
--
955715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#955715: closed by Alastair McKinstry (FIxed in toolchain)
Control: notfound -1 adios/1.13.1-21 Control: severity -1 normal On 4/22/20 12:42 PM, Debian Bug Tracking System wrote: > This was caused due to errors in the OpenMPI toolchain, which have since > been fixed. > > Adios builds Just closing the bug is not sufficient, it's still marked as affecting the version in testing. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#952300: marked as done (construct: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequenc
Your message dated Wed, 22 Apr 2020 10:48:37 + with message-id and subject line Bug#952300: fixed in construct 2.8.16-0.4 has caused the Debian Bug report #952300, regarding construct: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 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 (eval 3) line 1. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 952300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: construct Version: 2.8.16-0.3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > dh clean --with python3 --buildsystem=pybuild > dh: warning: Compatibility levels before 9 are deprecated (level 8 in use) > dh: error: unable to load addon python3: Can't locate > Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the > Debian::Debhelper::Sequence::python3 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 (eval 3) > line 1. > BEGIN failed--compilation aborted at (eval 3) line 1. > > make: *** [debian/rules:11: clean] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/02/22/construct_2.8.16-0.3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: construct Source-Version: 2.8.16-0.4 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of construct, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated construct package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 07 Apr 2020 12:52:26 +0300 Source: construct Architecture: source Version: 2.8.16-0.4 Distribution: unstable Urgency: medium Maintainer: Jonathan Wiltshire Changed-By: Adrian Bunk Closes: 952300 Changes: construct (2.8.16-0.4) unstable; urgency=medium . * Non-maintainer upload. * Add the now required build dependency on dh-python. (Closes: #952300) Checksums-Sha1: 99430500c74c573999c502abb3b1d7f6cf9fd0f9 1961 construct_2.8.16-0.4.dsc b4769ad26612d37f215a3c22e3114d8db3116b78 2776 construct_2.8.16-0.4.debian.tar.xz Checksums-Sha256: 2957a610d65aae351e0c1e6a970ca2c2e15b0519c879dbc2c9702c4316f48302 1961 construct_2.8.16-0.4.dsc 5355056eb2d5236743e38bdff16ba967acbf0845a984dcd09165f8b9f68f82e6 2776 construct_2.8.16-0.4.debian.tar.xz Files: 38c372f9945ae19a7bf292463ee541ff 1961 python extra construct_2.8.16-0.4.dsc fc7629971b57f037c93c80d160a3d248 2776 python extra construct_2.8.16-0.4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl6MTcAACgkQiNJCh6LY mLEOtA//TAZNtMkKLZD2d/ZrhkDEwkkML3YybfkkHH6rkR10mAhItRaFCUlNxePA LnymlLVMsRcPyJMl92nqR1qYF3Vek2fzsa8/Ak0m8FEP84NFAS36HIUVMdaqFM7n 4rLCjJJuJ4QDXfM+foLfEwvMgYAE35lBZwkE3aWrQmGqdyMxvgqU31CdA0EI3j3I 5b2TXQbJKftO8VYrAmC+uKwU5YwtofZE3qI5A0GZOM3yRXXm6owSiD1/y+WAb8sX EqXn0NFGkfg/n7XrKuIT5pMLc7JYiENSCYjLnBaPuPiYp2lwWgh9GgwireSV7SKx
Bug#937144: Bug#952130: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).
Hi, út 21. 4. 2020 v 23:24 odesílatel Thomas Goirand napsal: > > But that still leaves the question of what to do about the dependency of > > pytest on pypy-funcsigs ? should pypy modules be removed from pytest and > > it's reverse-dependencies in the same way that regular python2 modules > > were? how feasible is that? are pypy-* packages only useful with python2 > > pypy or are they also useful with python3 pypy? > > I really don't know about pypy. Probably the pypy-pytest should indeed > go away, as the initial plan was to switch to pypy3. Maybe tumbleweed > (Stefano Rivera) would be able to answer. I'm adding him as Cc. > I guess I can say something about pytest because I'm maintainer of pytest, right? :) I'm perfectly fine with removing pypy-pytest binary package and all other dependencies in chain. It's painfull to maintain it. -- Best regards Ondřej Nový
Bug#958450: chromium: Please update chromium to 81.0.4044.113 for security reasons
Package: chromium Version: 81.0.4044.92-1 Severity: grave Tags: upstream security Justification: user security hole Dear Maintainer, As the title suggests, please update chromium to 81.0.4044.113 (or later), because it includes a patch for CVE-2020-6457, which is a critical security issue. More info here https://chromereleases.googleblog.com/2020/04/stable-channel-update-for- desktop_15.html -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-1-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages chromium depends on: ii chromium-common 81.0.4044.92-1 ii libasound2 1.2.2-2.1 ii libatk-bridge2.0-0 2.34.1-3 ii libatk1.0-0 2.36.0-2 ii libatspi2.0-02.36.0-2 ii libavcodec58 10:4.2.2-dmo7 ii libavformat5810:4.2.2-dmo7 ii libavutil56 10:4.2.2-dmo7 ii libc62.30-4 ii libcairo21.16.0-4 ii libcups2 2.3.1-11 ii libdbus-1-3 1.12.16-2 ii libdrm2 2.4.101-2 ii libevent-2.1-7 2.1.11-stable-1 ii libexpat12.2.9-1 ii libflac8 1.3.3-1 ii libfontconfig1 2.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgbm1 19.3.3-1 ii libgcc-s110-20200411-1 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-4 ii libglib2.0-0 2.64.1-1 ii libgtk-3-0 3.24.18-1 ii libharfbuzz0b2.6.4-1 ii libicu63 63.2-3 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libjsoncpp1 1.7.4-3.1 ii liblcms2-2 2.9-4+b1 ii libminizip1 1.1-8+b1 ii libnspr4 2:4.25-1 ii libnss3 2:3.51-1 ii libopenjp2-7 2.3.1-1 ii libopus0 1.3-1+b1 ii libpango-1.0-0 1.44.7-3 ii libpangocairo-1.0-0 1.44.7-3 ii libpng16-16 1.6.37-2 ii libpulse013.0-5 ii libre2-6 20200401+dfsg-1 ii libsnappy1v5 1.1.8-1 ii libstdc++6 10-20200411-1 ii libvpx6 1.8.2-dmo1 ii libwebp6 0.6.1-2+b1 ii libwebpdemux20.6.1-2+b1 ii libwebpmux3 0.6.1-2+b1 ii libx11-6 2:1.6.9-2 ii libx11-xcb1 2:1.6.9-2 ii libxcb-dri3-01.14-2 ii libxcb1 1.14-2 ii libxcomposite1 1:0.4.5-1 ii libxcursor1 1:1.2.0-2 ii libxdamage1 1:1.1.5-2 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-2 ii libxi6 2:1.7.9-1 ii libxml2 2.9.10+dfsg-4 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.1 1.1.34-4 ii libxss1 1:1.2.3-1 ii libxtst6 2:1.2.3-1 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages chromium recommends: pn chromium-sandbox Versions of packages chromium suggests: pn chromium-driver pn chromium-l10n pn chromium-shell Versions of packages chromium-common depends on: ii x11-utils 7.7+5 ii xdg-utils 1.1.3-2 Versions of packages chromium-common recommends: pn chromium-sandbox ii dunst [notification-daemon] 1.4.1-1 ii fonts-liberation 1:1.07.4-11 ii libgl1-mesa-dri 19.3.3-1 pn libu2f-udev ii notification-daemon 3.20.0-4 pn system-config-printer pn upower -- no debconf information
Bug#958446: nvidia-legacy-340xx-driver: Fails to build with kernel 5.6
Package: nvidia-legacy-340xx-driver Version: 340.108-4 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, As with my previous bug reports, nvidia legacy 340 fails to build again. Here is the full log https://pastebin.com/i5wR0s5V Here is the patch, again from aur https://aur.archlinux.org/cgit/aur.git/plain/05-unfuck-for- kernel-5.6.x.patch?h=nvidia-340xx Unlike last time with 5.5, it seems that it patches a number of files and I do not know how to do it myself, so I can't test it. -- Package-specific info: uname -a: Linux mitsos 5.5.0-1-amd64 #1 SMP Debian 5.5.13-2 (2020-03-30) x86_64 GNU/Linux /proc/version: Linux version 5.5.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 (Debian 9.3.0-8)) #1 SMP Debian 5.5.13-2 (2020-03-30) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Debian 9.3.0-10) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: [0.319340] Console: colour VGA+ 80x25 [0.750070] pci :01:00.0: vgaarb: setting as boot VGA device [0.750070] pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [0.750070] pci :01:00.0: vgaarb: bridge control possible [0.750070] vgaarb: loaded [0.934312] Linux agpgart interface v0.103 [3.385956] nvidia: loading out-of-tree module taints kernel. [3.385967] nvidia: module license 'NVIDIA' taints kernel. [3.412258] nvidia: module verification failed: signature and/or required key missing - tainting kernel [3.423284] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [3.440267] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [3.440279] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 [3.922930] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [5.136035] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input17 [5.136119] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input18 [5.136192] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input19 [5.136267] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input25 [7.384689] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs Device node permissions: crw-rw+ 1 root video 226, 0 Apr 22 10:16 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Apr 22 10:16 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Apr 22 10:16 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Apr 22 10:16 pci-:01:00.0-card -> ../card0 video:*:44:jim OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Jan 5 09:29 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 44 Jan 5 09:29 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 lrwxrwxrwx 1 root root 43 Jan 5 09:29 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Jan 5 09:29 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 54 Jan 5 09:29 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 lrwxrwxrwx 1 root root 54 Jan 5 09:29 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 lrwxrwxrwx 1 root root 25 Jan 5 09:29 /etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 42 Jan 5 09:29 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> /etc/nvidia/nvidia-blacklists-nouveau.conf lrwxrwxrwx 1 root root 36 Jan 5 09:29 /etc/alternatives/glx--nvidia-bug-report.sh -> /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 39 Jan 5 09:29 /etc/alternatives/glx--nvidia-drm-outputclass.conf -> /etc/nvidia/nvidia-drm-outputclass.conf lrwxrwxrwx 1 root root 28 Jan 5 09:29 /etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf lrwxrwxrwx 1 root root 32 Jan 5 09:29 /etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf lrwxrwxrwx 1 root root 29
Bug#955694: scilab: FTBFS: Scilab cannot create Scilab Java Main-Class (we have not been able to find the main Scilab class. Check if the Scilab and thirdparty packages are available).
Le 22/04/2020 à 09:59, Gilles Filippini a écrit : Hi, Matthias Klose a écrit le 20/04/2020 à 12:49 : On 4/20/20 11:52 AM, Gilles Filippini wrote: I'd like to do a bisect between openjdk-11 11.0.6+10-2 and 11.0.7+9-1 to better understand the problem but I can't find the corresponding branch on the openjdk Mercurial repo. http://hg.openjdk.java.net/jdk-updates/jdk11u/ This commit is the culprit: http://hg.openjdk.java.net/jdk-updates/jdk11u/rev/21710e014d7f It makes sense since it is related to System.loadLibrary(). Because Scilab loads Java from C++ code I guess moving usr_paths ans sys_paths initialization out of System.loadLibrary might have some consequences. Applying the attached patch to openjdk-11 solves the problem. Not sure this is the right thing to do, but it keeps the deadlock fix brought by the jdk changeset and allows for sys_paths and usr_paths initialization in System.loadLibrary() when needed. @doko, please consider adding this patch to the openjdk-11 source package until a proper fix is found for Scilab. + upstream Cheers S
Bug#955694: scilab: FTBFS: Scilab cannot create Scilab Java Main-Class (we have not been able to find the main Scilab class. Check if the Scilab and thirdparty packages are available).
Hi,
Matthias Klose a écrit le 20/04/2020 à 12:49 :
> On 4/20/20 11:52 AM, Gilles Filippini wrote:
>> I'd like to do a bisect between openjdk-11 11.0.6+10-2 and 11.0.7+9-1 to
>> better understand the problem but I can't find the corresponding branch
>> on the openjdk Mercurial repo.
>
> http://hg.openjdk.java.net/jdk-updates/jdk11u/
>
This commit is the culprit:
http://hg.openjdk.java.net/jdk-updates/jdk11u/rev/21710e014d7f
It makes sense since it is related to System.loadLibrary().
Because Scilab loads Java from C++ code I guess moving usr_paths ans
sys_paths initialization out of System.loadLibrary might have some
consequences.
Applying the attached patch to openjdk-11 solves the problem. Not sure
this is the right thing to do, but it keeps the deadlock fix brought by
the jdk changeset and allows for sys_paths and usr_paths initialization
in System.loadLibrary() when needed.
@doko, please consider adding this patch to the openjdk-11 source
package until a proper fix is found for Scilab.
Thanks,
_g.
Index: openjdk-11-11.0.7+10/src/java.base/share/classes/java/lang/ClassLoader.java
===
--- openjdk-11-11.0.7+10.orig/src/java.base/share/classes/java/lang/ClassLoader.java
+++ openjdk-11-11.0.7+10/src/java.base/share/classes/java/lang/ClassLoader.java
@@ -2620,9 +2620,10 @@ public abstract class ClassLoader {
boolean isAbsolute) {
ClassLoader loader =
(fromClass == null) ? null : fromClass.getClassLoader();
-assert sys_paths != null : "should be initialized at this point";
-assert usr_paths != null : "should be initialized at this point";
-
+if (sys_paths == null) {
+usr_paths = initializePath("java.library.path");
+sys_paths = initializePath("sun.boot.library.path");
+}
if (isAbsolute) {
if (loadLibrary0(fromClass, new File(name))) {
return;
Bug#953487: Bugs fixed in runescape/0.8-1
Hi, Improvements were made to the Runescape launcher, as reported. BUG #953487: - This bug contains "XS-Autobuild: yes" in d/control and also a warning about "Autobuilding" in d/copyright since the runescape/0.5-2 package which has not been changed since recent versions. BUG #956275: - Own icon created in SVG and PNG formats for this runescape launcher. BUG #956276: - Added in the script (runescape.sh) the integrity check with the hashsum of the downloaded file. - Added warning message via kdialog or zenity when executing the script, explaining what it does. Thanks see you soon! -- ⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao] ⣾⠁⢠⠒⠀⣿⡁ Debian Wiki: https://wiki.debian.org/coringao ⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780 ⠈⠳⣄⠀⠀⠀ 2157 630B D441 A775 BEFF D35F FA63 ADA6 B638 B780 signature.asc Description: This is a digitally signed message part
Bug#958430: (no subject)
Thank you for your interest in the vagrant boxes. A fresh vagrant env with libvirt and 10.3 works for me (see: http://paste.debian.net/1142057/) Can you reproduce the problem in a fresh environment ? ie erase your current box and create a new vagrant env vagrant box remove debian/buster64 vagrant init debian/buster64 vagrant up --provider=libvirt and post here the commands output. -- /* parttimelog.wordpress.com Part time pictures */
Bug#958430: Vagrant libvirt
Thank you for your interest in the vagrant boxes. A fresh vagrant env with libvirt and 10.3 works for me (see: http://paste.debian.net/1142057/) Can you reproduce the problem in a fresh environment ? ie erase your current box and create a new vagrant env vagrant box remove debian/buster64 vagrant init debian/buster64 vagrant up --provider=libvirt and post here the commands output.
Bug#942988: displaycal: Python2 removal in sid/bullseye
On 17 avril 2020 11:32, Scott Talbert wrote: [...] > It looks like upstream doesn't seem to be making much progress on > this. Do you think that we need to start working on Python 3 support > ourselves? Duplicate work is a bad idea. Otherwise upstream is still active in displaycal forums (18/04/2020) : https://hub.displaycal.net/forums/topic/battery-life/ Christian
