Bug#950155: marked as done (apertium-oc-ca FTBFS with apertium 3.6.1)

[Debian Bug Tracking System]

Your message dated Thu, 26 Mar 2020 05:04:14 +
with message-id 
and subject line Bug#950155: fixed in apertium-oc-ca 1.0.6~r57551-4
has caused the Debian Bug report #950155,
regarding apertium-oc-ca FTBFS with apertium 3.6.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.)


-- 
950155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-oc-ca
Version: 1.0.6~r57551-3
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-oc-ca.html

...
   dh_auto_build -O--fail-missing
make -j15
make[1]: Entering directory '/build/1st/apertium-oc-ca-1.0.6~r57551'
make  all-am
make[2]: Entering directory '/build/1st/apertium-oc-ca-1.0.6~r57551'
xsltproc --stringparam alt oc alt.xsl apertium-oc-ca.oc.metadix 
>.deps/oc.metadix
xsltproc --stringparam alt oc alt.xsl apertium-oc-ca.ca.dix >.deps/ca.dix
xsltproc --stringparam alt oc alt.xsl apertium-oc-ca.oc-ca.dix >.deps/oc-ca.dix
xsltproc --stringparam alt oc alt.xsl apertium-oc-ca.post-ca.dix 
>.deps/ca.post.dix
xsltproc --stringparam alt oc alt.xsl apertium-oc-ca.post-oc.dix 
>.deps/oc.post.dix
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-ca.oc.metadix 
>.deps/oc@aran.metadix
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-ca.ca.dix 
>.deps/c...@aran.dix
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-ca.oc-ca.dix 
>.deps/o...@aran-ca.dix
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-ca.post-ca.dix 
>.deps/c...@aran.post.dix
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-ca.post-oc.dix 
>.deps/o...@aran.post.dix
xsltproc --stringparam alt oc alt.xsl apertium-oc-ca.oc-ca.t1x > oc-ca.t1x
xsltproc --stringparam alt oc alt.xsl apertium-oc-ca.oc-ca.t2x > oc-ca.t2x
xsltproc --stringparam alt oc alt.xsl apertium-oc-ca.oc-ca.t3x > oc-ca.t3x
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-ca.oc-ca.t1x > 
oc@aran-ca.t1x
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-ca.oc-ca.t2x > 
oc@aran-ca.t2x
apertium-validate-postchunk oc-ca.t3x
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-ca.oc-ca.t3x > 
oc@aran-ca.t3x
xsltproc --stringparam alt oc alt.xsl apertium-oc-ca.ca-oc.t1x > ca-oc.t1x
apertium-validate-interchunk oc-ca.t2x
xsltproc --stringparam alt oc alt.xsl apertium-oc-ca.ca-oc.t2x > ca-oc.t2x
apertium-validate-interchunk oc@aran-ca.t2x
apertium-validate-postchunk oc@aran-ca.t3x
xsltproc --stringparam alt oc alt.xsl apertium-oc-ca.ca-oc.t3x > ca-oc.t3x
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-ca.ca-oc.t1x > 
ca-oc@aran.t1x
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-ca.ca-oc.t2x > 
ca-oc@aran.t2x
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-ca.ca-oc.t3x > 
ca-oc@aran.t3x
apertium-validate-modes modes.xml
apertium-validate-postchunk ca-oc.t3x
apertium-gen-modes modes.xml
apertium-validate-postchunk ca-oc@aran.t3x
apertium-validate-dictionary .deps/ca.post.dix
apertium-validate-interchunk ca-oc.t2x
apertium-validate-dictionary .deps/oc.post.dix
apertium-validate-interchunk ca-oc@aran.t2x
apertium-validate-dictionary .deps/c...@aran.post.dix
lt-comp lr .deps/ca.post.dix oc-ca.autopgen.bin
cp *.mode modes/
lt-comp lr .deps/oc.post.dix ca-oc.autopgen.bin
apertium-validate-dictionary .deps/o...@aran.post.dix
cp: cannot stat '*.mode': No such file or directory
make[2]: *** [Makefile:958: modes/oc-ca.mode] Error 1
--- End Message ---
--- Begin Message ---
Source: apertium-oc-ca
Source-Version: 1.0.6~r57551-4
Done: Kartik Mistry 

We believe that the bug you reported is fixed in the latest version of
apertium-oc-ca, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 950...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated apertium-oc-ca package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 26 Mar 2020 08:54:46 +0530
Source: apertium-oc-ca
Architecture: source
Version: 1.0.6~r57551-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Closes: 950155
Changes:
 

Bug#952070: marked as done (ruby-puppetlabs-spec-helper: FTBFS: ERROR: Test "ruby2.5" failed: Failure/Error: Puppet::Parser::Functions.expects(:function).with('my_func').returns(false))

[Debian Bug Tracking System]

Your message dated Thu, 26 Mar 2020 04:20:04 +
with message-id 
and subject line Bug#952070: fixed in ruby-puppetlabs-spec-helper 2.6.2-2
has caused the Debian Bug report #952070,
regarding ruby-puppetlabs-spec-helper: FTBFS: ERROR: Test "ruby2.5" failed: 
Failure/Error: 
Puppet::Parser::Functions.expects(:function).with('my_func').returns(false)
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.)


-- 
952070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-puppetlabs-spec-helper
Version: 2.6.2-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):
>  Failure/Error: 
> Puppet::Parser::Functions.expects(:function).with('my_func').returns(false)
> 
>  Mocha::NotInitializedError:
>Mocha methods cannot be used outside the context of a test
>  # 
> ./spec/unit/puppetlabs_spec_helper/puppetlabs_spec/puppet_internals_spec.rb:96:in
>  `block (3 levels) in '
> 
> Deprecation Warnings:
> 
> scope is deprecated. Use rspec-puppet 2.2.0 provides a scope property 
> instead. Called from 
> /<>/lib/puppetlabs_spec_helper/puppetlabs_spec/puppet_internals.rb:11:in
>  `scope'.
> 
> 
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
> 
> 1 deprecation warning total
> 
> Finished in 0.06403 seconds (files took 0.80944 seconds to load)
> 21 examples, 2 failures
> 
> Failed examples:
> 
> rspec 
> ./spec/unit/puppetlabs_spec_helper/puppetlabs_spec/puppet_internals_spec.rb:88
>  # PuppetlabsSpec::PuppetInternals.function_method accepts an injected scope
> rspec 
> ./spec/unit/puppetlabs_spec_helper/puppetlabs_spec/puppet_internals_spec.rb:95
>  # PuppetlabsSpec::PuppetInternals.function_method returns nil if the 
> function doesn't exist
> 
> /usr/bin/ruby2.5 
> -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.5" failed: 

The full build log is available from:
   
http://qa-logs.debian.net/2020/02/22/ruby-puppetlabs-spec-helper_2.6.2-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-puppetlabs-spec-helper
Source-Version: 2.6.2-2
Done: Daniel Leidert 

We believe that the bug you reported is fixed in the latest version of
ruby-puppetlabs-spec-helper, 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-puppetlabs-spec-helper 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, 26 Mar 2020 04:55:25 +0100
Source: ruby-puppetlabs-spec-helper
Architecture: source
Version: 2.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Daniel Leidert 
Closes: 952070
Changes:
 ruby-puppetlabs-spec-helper (2.6.2-2) unstable; urgency=medium
 .
   * Team upload.
   * d/compat: Remove obsolete file.
   * d/control: Add Testsuite and Rules-Requires-Root field.
 (Build-Depends): Use debhelper-compat version 12. Add ruby-sync.
 (Standards-Version): Bump to 4.5.0.
 (Depends): Use ${ruby:Depends} and remove interpreter.
   * d/rules: Add override to install upstream Changelog.md.
   * d/watch: Rewrite tarball name.
   * 

Bug#952078: marked as done (ruby-dalli: FTBFS: ERROR: Test "ruby2.7" failed.)

[Debian Bug Tracking System]

Your message dated Thu, 26 Mar 2020 04:05:53 +0100
with message-id <0ac1a5dd2c7fab5312d5f0f7866ef95f371009da.ca...@debian.org>
and subject line Unreproducible, possibly caused by different package
has caused the Debian Bug report #952078,
regarding ruby-dalli: FTBFS: ERROR: Test "ruby2.7" failed.
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.)


-- 
952078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-dalli
Version: 2.7.9-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):
> /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.7  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-dalli/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 -e gem\ \"dalli\"
> 
> ┌──┐
> │ Run tests for ruby2.7 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-dalli/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/<>/debian/ruby-dalli/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.7 -w -I"test"  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/benchmark_test.rb" 
> -v
> /usr/lib/ruby/2.7.0/bundler/spec_set.rb:86:in `block in materialize': Could 
> not find rdoc-6.0.1.1 in any of the sources (Bundler::GemNotFound)
>   from /usr/lib/ruby/2.7.0/bundler/spec_set.rb:80:in `map!'
>   from /usr/lib/ruby/2.7.0/bundler/spec_set.rb:80:in `materialize'
>   from /usr/lib/ruby/2.7.0/bundler/definition.rb:170:in `specs'
>   from /usr/lib/ruby/2.7.0/bundler/definition.rb:237:in `specs_for'
>   from /usr/lib/ruby/2.7.0/bundler/definition.rb:226:in `requested_specs'
>   from /usr/lib/ruby/2.7.0/bundler/runtime.rb:101:in `block in 
> definition_method'
>   from /usr/lib/ruby/2.7.0/bundler/runtime.rb:20:in `setup'
>   from /usr/lib/ruby/2.7.0/bundler.rb:149:in `setup'
>   from /usr/lib/ruby/2.7.0/bundler/setup.rb:20:in `block in  (required)>'
>   from /usr/lib/ruby/2.7.0/bundler/ui/shell.rb:136:in `with_level'
>   from /usr/lib/ruby/2.7.0/bundler/ui/shell.rb:88:in `silence'
>   from /usr/lib/ruby/2.7.0/bundler/setup.rb:20:in `'
>   from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in 
> `require'
>   from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in 
> `require'
>   from /<>/test/helper.rb:3:in `'
>   from /<>/test/benchmark_test.rb:2:in `require_relative'
>   from /<>/test/benchmark_test.rb:2:in `'
>   from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in 
> `require'
>   from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in 
> `require'
>   from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:17:in `block in 
> '
>   from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:5:in `select'
>   from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:5:in `'
> rake aborted!
> Command failed with status (1): [ruby -w -I"test"  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/benchmark_test.rb" 
> -v]
> 
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.7" failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/ruby-dalli_2.7.9-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 ---
I am closing this report. The source 

Bug#954756: marked as done (puppet-module-aboe-chrony depends on obsolete transitional package.)

[Debian Bug Tracking System]

Your message dated Thu, 26 Mar 2020 02:21:00 +
with message-id <9195a083-bf5c-579a-4cd4-6f2c7bc6a...@p10link.net>
and subject line re: puppet-module-aboe-chrony depends on obsolete transitional 
package.
has caused the Debian Bug report #954756,
regarding puppet-module-aboe-chrony depends on obsolete transitional package.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: puppet-module-aboe-chrony
Version: 0.2.4-2
Severity: serious

puppet-module-aboe-chrony depends on the puppet-common transitional package 
which is no longer built by the puppet source package. Please update your 
dependencies.
--- End Message ---
--- Begin Message ---

Version: 0.2.4-4

This was fixed as part of a bulk update/upload by Thomas Goirand.--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 954470 + patch
Bug #954470 [src:pysha3] src:pysha3: Autopkgtest failure due to use of 
py3versions -i
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954470: pysha3: Autopkgtest failure due to use of py3versions -i

[eamanu]

Hi,

I attach a NMU patch. Please, consider apply it.

Thanks

Cheers,

-- 
Emmanuel Arias
@eamanu
yaerobi.com
From db724cd1aa5c7bc37c9210e3cdf5a2c252ae504d Mon Sep 17 00:00:00 2001
From: Emmanuel Arias 
Date: Wed, 25 Mar 2020 23:04:36 -0300
Subject: [PATCH] pysha3: fix autopkgtest regression.

Use pyversions -s to test all suported version.
---
 debian/changelog   | 8 
 debian/tests/control   | 3 ++-
 debian/tests/smoke-python3 | 2 +-
 3 files changed, 11 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index c5c4363..4c79179 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+pysha3 (1.0.2-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/tests/smoke-python3: Fix autopkgtest regression.
+Use pyversions -s to test all suported version (Closes: #954470).
+
+ -- Emmanuel Arias   Wed, 25 Mar 2020 23:04:41 -0300
+
 pysha3 (1.0.2-4) unstable; urgency=medium
 
   * Declare Debhelper compatibility using ‘debhelper-compat’ dependency.
diff --git a/debian/tests/control b/debian/tests/control
index c522629..6f8102c 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -5,7 +5,8 @@
 Tests: smoke-python3
 Depends:
 python3-pkg-resources,
-python3-sha3
+python3-sha3,
+python3-all
 
 
 # Local variables:
diff --git a/debian/tests/smoke-python3 b/debian/tests/smoke-python3
index b01681e..4358597 100644
--- a/debian/tests/smoke-python3
+++ b/debian/tests/smoke-python3
@@ -24,7 +24,7 @@ for mod in ${MODULE_NAMES[@]} ; do
 test_opts="$test_opts --module=$mod"
 done
 
-for py in $(py3versions -i) ; do
+for py in $(py3versions -s) ; do
 printf "Python command: %s\n" $py
 $py debian/tests/smoke_test.py $test_opts
 printf "\n"
-- 
2.25.1



0xFA9DEC5DE11C63F1.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 954461 + patch
Bug #954461 [src:editorconfig-core-py] src:editorconfig-core-py: Autopkgtest 
failure due to use of py3versions -i
Ignoring request to alter tags of bug #954461 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 954468 + patch
Bug #954468 [src:pyethash] src:pyethash: Autopkgtest failure due to use of 
py3versions -i
Added tag(s) patch.
> tags 954469 + patch
Bug #954469 [src:pyrlp] src:pyrlp: Autopkgtest failure due to use of 
py3versions -i
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954468
954469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 954461 954468 954469 + patch
Unknown tag/s: 954468, 954469.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore.

Bug #954461 [src:editorconfig-core-py] src:editorconfig-core-py: Autopkgtest 
failure due to use of py3versions -i
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954469: src:pyrlp: Autopkgtest failure due to use of py3versions -i

[eamanu]

Hi,

I attach a NMU patch. Please, consider apply it.

Thanks!

Cheers,

-- 
Emmanuel Arias
@eamanu
yaerobi.com
From 05d4ad3f70ed004e4d4bee65fa39c302b02ad640 Mon Sep 17 00:00:00 2001
From: Emmanuel Arias 
Date: Wed, 25 Mar 2020 22:12:31 -0300
Subject: [PATCH] pyrlp: Fix autopkgtest regression.

Use pyversions -s to test all suported versions.
---
 debian/changelog   | 8 
 debian/tests/control   | 3 ++-
 debian/tests/smoke-python3 | 2 +-
 3 files changed, 11 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 9a78b0f..eb2d496 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+pyrlp (0.5.1-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/tests/smoke-python3: Fix autopkgtest regression.
+Use pyversions -s to test all suported versions (Closes: #954469).
+
+ -- Emmanuel Arias   Wed, 25 Mar 2020 22:12:44 -0300
+
 pyrlp (0.5.1-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --git a/debian/tests/control b/debian/tests/control
index 1a50271..e92292f 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -5,7 +5,8 @@
 Tests: smoke-python3
 Depends:
 python3-pkg-resources,
-python3-rlp
+python3-rlp,
+python3-all
 
 
 # Local variables:
diff --git a/debian/tests/smoke-python3 b/debian/tests/smoke-python3
index b9155f7..ffddf53 100755
--- a/debian/tests/smoke-python3
+++ b/debian/tests/smoke-python3
@@ -26,7 +26,7 @@ for mod in ${MODULE_NAMES[@]} ; do
 test_opts="$test_opts --module=$mod"
 done
 
-for py in $(py3versions -i) ; do
+for py in $(py3versions -s) ; do
 printf "Python command: %s\n" $py
 $py debian/tests/smoke_test.py $test_opts
 printf "\n"
-- 
2.25.1



0xFA9DEC5DE11C63F1.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Processed: Bug#954948 marked as pending in fonts-noto

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954948 [fonts-noto] [d-i bullseye alpha2] Sinhala font missing
Added tag(s) pending.

-- 
954948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954948: marked as pending in fonts-noto

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

Bug #954948 in fonts-noto 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/fonts-team/fonts-noto/-/commit/cf3d2b40bad2ccd42800ab833c6bbc63f75c79dd


fix include SinhalaSans in udeb (accidentally dropped since 20200103-1); 
closes: bug#954948, thanks to Holger Wansing


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954948

Bug#954468: src:pyethash: Autopkgtest failure due to use of py3versions -i

[eamanu]

Hi,

I attach a NMU patch. Please, consider apply it.

Thanks!

Cheers,

-- 
Emmanuel Arias
@eamanu
yaerobi.com
From 86054609e4f0c6526fdb21ebe6fd90088366ec62 Mon Sep 17 00:00:00 2001
From: Emmanuel Arias 
Date: Wed, 25 Mar 2020 21:56:15 -0300
Subject: [PATCH] pyethash: d/tests/smoke-python3: fix autopkgtest regression.

Use pyversions -s to test all suported versions.

---
 debian/changelog   | 8 
 debian/tests/control   | 3 ++-
 debian/tests/smoke-python3 | 2 +-
 3 files changed, 11 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 7783c95..40adcd7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+pyethash (0.1.27-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/tests/smoke-python3: fix autopkgtest regression.
+Use pyversions -s to test all suported versions (Closes: #954468).
+
+ -- Emmanuel Arias   Wed, 25 Mar 2020 21:56:25 -0300
+
 pyethash (0.1.27-2) unstable; urgency=medium
 
   [ Ben Finney ]
diff --git a/debian/tests/control b/debian/tests/control
index f3c4053..9661185 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -5,7 +5,8 @@
 Tests: smoke-python3
 Depends:
 python3-pkg-resources,
-python3-pyethash
+python3-pyethash,
+python3-all
 
 
 # Local variables:
diff --git a/debian/tests/smoke-python3 b/debian/tests/smoke-python3
index 7092cd9..d043aec 100755
--- a/debian/tests/smoke-python3
+++ b/debian/tests/smoke-python3
@@ -24,7 +24,7 @@ for mod in ${MODULE_NAMES[@]} ; do
 test_opts="$test_opts --module=$mod"
 done
 
-for py in $(py3versions -i) ; do
+for py in $(py3versions -s) ; do
 printf "Python command: %s\n" $py
 $py debian/tests/smoke_test.py $test_opts
 printf "\n"
-- 
2.25.1



0xFA9DEC5DE11C63F1.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#954533: This is likely libssl1.1 problem

[Iustin Pop]

This happens in othe packages - well, not the FTBFS, but the error, like
getmail. It's been reported in other distros as well, e.g. see
https://bugs.archlinux.org/task/65976.

Maybe re-assign to libssl1.1?

Bug#952027: marked as done (ruby-declarative: FTBFS: ERROR: Test "ruby2.5" failed: Invalid gemspec in [declarative.gemspec]: No such file or directory - git)

[Debian Bug Tracking System]

Your message dated Thu, 26 Mar 2020 00:49:48 +
with message-id 
and subject line Bug#952027: fixed in ruby-declarative 0.0.10-2
has caused the Debian Bug report #952027,
regarding ruby-declarative: FTBFS: ERROR: Test "ruby2.5" failed: Invalid 
gemspec in [declarative.gemspec]: No such file or directory - git
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.)


-- 
952027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-declarative
Version: 0.0.10-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):
> Invalid gemspec in [declarative.gemspec]: No such file or directory - git
> GEM_PATH=/<>/debian/ruby-declarative/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0
>  ruby2.5 -e gem\ \"declarative\"
> 
> ┌──┐
> │ Run tests for ruby2.5 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-declarative/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/<>/debian/ruby-declarative/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0
>  ruby2.5 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.5 -w -I"test"  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/defaults_test.rb" 
> "test/definitions_test.rb" "test/heritage_test.rb" "test/schema_test.rb" 
> "test/variables_test.rb" "test/test_helper.rb" -v
> Run options: -v --seed 45730
> 
> # Running:
> 
> multiple Defaults#merge!#test_0001_merges arrays automatically = DEPRECATED: 
> global use of must_equal from /<>/test/defaults_test.rb:68. Use 
> _(obj).must_equal instead. This will fail in Minitest 6.
> 0.00 s = .
> multiple Defaults#merge!#test_0002_what = DEPRECATED: global use of 
> must_equal from /<>/test/defaults_test.rb:76. Use 
> _(obj).must_equal instead. This will fail in Minitest 6.
> 0.00 s = .
> DefinitionTest#test_0001_#merge does return deep copy = DEPRECATED: global 
> use of must_equal from /<>/test/definitions_test.rb:93. Use 
> _(obj).must_equal instead. This will fail in Minitest 6.
> 0.00 s = .
> with only dynamic property options#test_0001_anonymous = DEPRECATED: global 
> use of must_equal from /<>/test/defaults_test.rb:32. Use 
> _(obj).must_equal instead. This will fail in Minitest 6.
> 0.00 s = .
> deprecation#test_0001_prints deprecation twice = 0.00 s = F
> DSLOptionsTest#test_0006_creates new array if original not existent = 
> DEPRECATED: global use of must_equal from 
> /<>/test/variables_test.rb:63. Use _(obj).must_equal instead. 
> This will fail in Minitest 6.
> DEPRECATED: global use of must_equal from 
> /<>/test/variables_test.rb:9. Use _(obj).must_equal instead. 
> This will fail in Minitest 6.
> 0.00 s = .
> DSLOptionsTest#test_0001_merges Merge over original = DEPRECATED: global use 
> of must_equal from /<>/test/variables_test.rb:19. Use 
> _(obj).must_equal instead. This will fail in Minitest 6.
> DEPRECATED: global use of must_equal from 
> /<>/test/variables_test.rb:9. Use _(obj).must_equal instead. 
> This will fail in Minitest 6.
> 0.00 s = .
> DSLOptionsTest#test_0004_creates new hash if original not existent = 
> DEPRECATED: global use of must_equal from 
> /<>/test/variables_test.rb:44. Use _(obj).must_equal instead. 
> This will fail in Minitest 6.
> DEPRECATED: global use of must_equal from 
> /<>/test/variables_test.rb:9. Use _(obj).must_equal instead. 
> This will fail in Minitest 6.
> 0.00 s = .
> DSLOptionsTest#test_0005_appends to Array = DEPRECATED: global use of 
> must_equal from /<>/test/variables_test.rb:54. Use 
> _(obj).must_equal instead. This will fail in Minitest 6.
> DEPRECATED: global use of must_equal from 
> /<>/test/variables_test.rb:9. Use _(obj).must_equal instead. 
> This will fail in Minitest 6.
> 0.00 s = .
> DSLOptionsTest#test_0002_accepts Procs = DEPRECATED: global use of must_equal 
> from /<>/test/variables_test.rb:28. Use _(obj).must_equal 
> instead. This will fail in Minitest 6.
> DEPRECATED: global use of must_equal from 
> 

Bug#950983: marked as done (clickhouse FTBFS in bullseye/sid)

[Debian Bug Tracking System]

Your message dated Thu, 26 Mar 2020 00:19:28 +
with message-id 
and subject line Bug#950983: fixed in clickhouse 18.16.1+ds-6
has caused the Debian Bug report #950983,
regarding clickhouse FTBFS in bullseye/sid
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.)


-- 
950983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clickhouse
Version: 18.16.1+ds-5
Severity: serious
Tags: ftbfs

Hi,

clickhouse fails to build from source in bullseye/sid:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/clickhouse.html

/build/1st/clickhouse-18.16.1+ds/dbms/src/Functions/intDiv.cpp:55:75: error: no 
match for 'operator/' (operand types are '__m128i' {aka '__vector(2) long long 
int'} and 'libdivide::divider')
   55 | _mm_loadu_si128(reinterpret_cast(a_pos)) / divider);
  | 
~~^
In file included from 
/build/1st/clickhouse-18.16.1+ds/dbms/src/Functions/intDiv.cpp:9:
/usr/include/libdivide.h:2039:3: note: candidate: 'template 
T libdivide::operator/(T, const libdivide::divider&)'
 2039 | T operator/(T n, const divider& div) {
  |   ^~~~
/usr/include/libdivide.h:2039:3: note:   template argument 
deduction/substitution failed:
/build/1st/clickhouse-18.16.1+ds/dbms/src/Functions/intDiv.cpp:55:75: note:   
deduced conflicting types for parameter 'T' ('__vector(2) long long int' and 
'unsigned int')
   55 | _mm_loadu_si128(reinterpret_cast(a_pos)) / divider);
  | 
~~^

I was able to reproduce this on my own system as well.
Would be great if you could fix this soon as it's blocking the poco
transition. One simple workaround would be to remove the #if __SSE2__
block (line 48-60) in intDiv.cpp as it's only a SSE2 optimization and
the generic case is below.

Cheers Jochen

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-3-amd64 (SMP w/8 CPU cores)
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
--- End Message ---
--- Begin Message ---
Source: clickhouse
Source-Version: 18.16.1+ds-6
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
clickhouse, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 950...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated clickhouse 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, 25 Mar 2020 19:56:10 -0400
Source: clickhouse
Architecture: source
Version: 18.16.1+ds-6
Distribution: unstable
Urgency: medium
Maintainer: Alexander GQ Gerasiov 
Changed-By: Sandro Tosi 
Closes: 950983
Changes:
 clickhouse (18.16.1+ds-6) unstable; urgency=medium
 .
   * debian/patches/fix-ftbfs.patch
 - Fix ftbfs with new mysql, new libdivide, patch by Dimitri John Ledkov;
   Closes: #950983
Checksums-Sha1:
 b15897d5aeb1c4581dc4c9ebd7b16b12f56d1fe1 3186 clickhouse_18.16.1+ds-6.dsc
 9d5ab17c149622c7e955e8e2849e6d62a330eadd 20720 
clickhouse_18.16.1+ds-6.debian.tar.xz
 cd4e9e66476b306e24d2281c7b8feb1274d4359b 12282 
clickhouse_18.16.1+ds-6_source.buildinfo
Checksums-Sha256:
 2f9db71debf940b72a21b7df77ca238fc8f01e76a220b911f8535683e61c 3186 
clickhouse_18.16.1+ds-6.dsc
 b862e87b83e3bcef755785874beddf208184e89c04e376e0332f78775cfc91b8 20720 
clickhouse_18.16.1+ds-6.debian.tar.xz
 fbf85d731407cd982eab6fb757fc215df78287b384903c1243063aae925b739d 12282 
clickhouse_18.16.1+ds-6_source.buildinfo
Files:
 089b46cadbc3c31ef2f0f1ce6e71 3186 database optional 
clickhouse_18.16.1+ds-6.dsc
 09a7f9dea7f42735fd070621b3061a7e 20720 database optional 
clickhouse_18.16.1+ds-6.debian.tar.xz
 8459b7e3bb5669fda1ebbba56e116a4b 12282 database optional 

Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>

[James McCoy]

On Wed, Mar 25, 2020 at 08:57:14AM -0400, Justin Erenkrantz wrote:
> James,
> 
> Thanks for the bug report.  For reference, the upstream OpenSSL commit looks 
> to
> be:
> 
> https://github.com/openssl/openssl/commit/
> d924dbf4ae127c68463bcbece04b6e06abc58928
> 
> I strongly suspect that the patch on our side (against 1.3.x) is something 
> akin
> to below.  I'm having trouble getting a test environment up with the latest
> OpenSSL to reproduce, so if anyone can test in the interim, that'd be
> appreciated.

Latest Debian sid has everything ready to test, although you'll need the
patch I'm carrying to build since SCons is using Python 3.  That reminds
me, I was supposed to send that to the list awhile back.

>   If not, I'll try again as time (and kiddo) permit.

Unfortunately, that didn't have any effect.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#943402: I have the same issue

[Fabio Muzzi]

I have exactly the same issue. Found it while trying to use Festival 
with Asterisk.




If I use the italian voice I get the same error, and if I use the 
english voice it works flawlessly.



Steps to reproduce:

install festlex-ifd and its dependencies.


run festival with italian language:

festival  --server -b --language italian

Try to use the Festival function in Asterisk

You will get no audio and festival will print an error that states 
"SIOD ERROR: wrong type of argument to get_c_utt"






--
Fabio "Kurgan" Muzzi

- IZ4UFQ -

"Il massimo danno con il minimo sforzo"

Bug#947564: FTBFS with scons 3.1.2-1

[Elías Alejandro]

Hello Jörg,
On Sat, Dec 28, 2019 at 08:51:25AM +0100, Jörg Frings-Fürst wrote:
> Source: gpick
> Version:  0.2.6~rc1-1
> Severity: important
> Usertags: scons_ftbfs
> 
> 
> Hello, 
> 
> in the context of the change to Python3 also Scons was revised. With
> the current version 3.1.2-1 from Experimental the changeover is
> finished so far. 
> 
> However, an error occurred while building your package. The build log
> is attached.
> 
> Please check it and fix the error.

Recent version of gpick 0.2.6~rc1-2 fix this bug. Now this version is into
unstable. You can also verify into[1]
[1] https://buildd.debian.org/status/package.php?p=gpick

If you are agree I'll close this bug. Please let me know.

Best regards,
Elías Alejandro

Processed: severity of 936659 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 936659 serious
Bug #936659 [src:gr-hpsdr] gr-hpsdr: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
936659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#920371: telnetd-ssl: SSL_CTX_use_certificate, ee key too small

[Marcos Marado]

Hi,

FYI, there is more info about this issue on
https://github.com/debauchee/barrier/issues/126 .

Best regards,
-- 
Marcos Marado

Bug#938622: tahoe-lafs: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Wed, Mar 18, 2020 at 10:38:17AM +0530, Vasudev Kamath wrote:
> 
> Sorry for the delayed response here. I let the package to fall of from
> testing as upstream does not yet any support for building python3.
> Though currently there is some work going on for supporting python3 in
> upstream, I'm not sure of ETA of the procedure.
> 
> Will reintroduce the package once upstream provides python3 support

tahoe-lafs also blocks the Python 2 migrations / removals of several
other packages in unstable (since it's pretty high up in the remaining
nested dependencies). If no Py3 port is foreseeable in the near future,
please rather remove it from unstable for now and reupload when it's
ported.

Cheers,
Moritz

Bug#954916: another breakage due to LaTeX changes?

[Joseph Wright]

On 25/03/2020 20:32, Norbert Preining wrote:

Hi Joseph,


See attached


Thanks (although order was reversed ;-)

Should we upload that to CTAN?

Best

Norbert


You can go for it; CTAN might not allow ...

Joseph

Bug#954916: another breakage due to LaTeX changes?

[Norbert Preining]

Hi Joseph,

> See attached

Thanks (although order was reversed ;-)

Should we upload that to CTAN?

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#954915: Error still not fixed

[Sina Ghaderi]

cat /etc/apt/sources.list
# deb http://deb.debian.org/debian/ sid main
deb http://deb.debian.org/debian/ sid main non-free contrib
# deb-src http://deb.debian.org/debian/ sid main non-free contrib

```
sudo apt full-upgrade
[sudo] password for sina:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  shim-unsigned
The following packages will be upgraded:
  cpp-9 gcc-9 gcc-9-base gir1.2-handy-0.0 gnome-disk-utility libasan5
libc-bin libc-l10n libc6
  libgcc-9-dev libhandy-0.0-0 libprotobuf-lite22 libprotobuf22 locales
14 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/33.5 MB of archives.
After this operation, 72.7 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 138600 files and directories currently installed.)
Preparing to unpack .../libc6_2.30-3_amd64.deb ...

A copy of the C library was found in an unexpected directory:
  '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
It is not safe to upgrade the C library in this situation;
please remove that copy of the C library or get it out of
'/usr/lib/x86_64-linux-gnu' and try again.

dpkg: error processing archive
/var/cache/apt/archives/libc6_2.30-3_amd64.deb (--unpack):
 new libc6:amd64 package pre-installation script subprocess returned error
exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.30-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
```

so i move this library thanks god i didn't delete it
after moving this file everything stop working , do not do that , please do
something about this

Bug#954954: libstdc++6: symbols file on armel incomplete

[Ivo De Decker]

package: libstdc++6
severity: serious

Hi,

It seems the symbols file for libstdc++6 is missing some symbols on armel. The
build adds these with the latest version. This causes new builds that use
these symbols to pick up an (unnecessary) versioned dependency on the latest
gcc in unstable.

As this bug sometimes causes testing migrations to block on the migration of
gcc, and thus interferes with transitions, I'm filing this as serious. This
currently is the case with the opencv binNMU on armel, which is blocked behind
gcc-10, blocking the python3-defauls transition.

Maybe the build should we configured to fail when new symbols are discovered,
to avoid similar issues in the future.

Thanks!

Ivo

Bug#951634: Broken package in testing repository

[Nilesh Patra]

Hi Alexander,  Hugo, Graham

On Wed, 25 Mar 2020, 21:45 Alexander van der Meij, <
vandermeij.t...@gmail.com> wrote:

>
>
>
> Hi Debian Science team,
>
> As described in bug 951634
> , Debian is
> currently distributing a broken development build of the software of which
> I am the developer; gummi.
>
> Hereby my request to either bump the package to the stable (0.8.1) release
> or remove it from your repositories altogether.
>

Alexander, Thank you for your work on Gummi.
I have fixed this, and updated to new version.

Please note that there are spelling mistakes in your package which lintian
pointed out, it would be great if you could  get it fixed with the new
release. See the patch here [1]

Hugo, Graham: the package builds in a clean chroot, and looks lintian clean
too.
I have pushed my changes here [2]

Could you please sponsor an upload?
That would be great!

[1]:
https://salsa.debian.org/science-team/gummi/-/blob/master/debian/patches/0001-spellings.patch

[2]: https://salsa.debian.org/science-team/gummi

Thanks and regards
Nilesh

>

Bug#954948: [d-i bullseye alpha2] Sinhala font missing

[Holger Wansing]

Control: reassign -1 fonts-noto


Holger Wansing  wrote:
> Package: debian-installer
> Severity: grave
> 
> 
> While testing the alpha2 netinst image I noticed that the graphical installer
> has no fonts for Sinhala anymore, this was ok until alpha1.
> 
> Screenshots attached.
> 


According to ../trunk/installer/build/pkg-lists/gtk-common 
d-i relies on 'fonts-noto-hinted-udeb' for Sinhala fonts.

Looking into that package, the current version for sid/bullseye is lacking
NotoSansSinhala-Bold.ttf
NotoSansSinhala-Regular.ttf
which exist in buster version.

Did that font files moved to another udeb?


Re-assigning to fonts-noto.

Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Processed: Re: Bug#954948: [d-i bullseye alpha2] Sinhala font missing

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 fonts-noto
Bug #954948 [debian-installer] [d-i bullseye alpha2] Sinhala font missing
Bug reassigned from package 'debian-installer' to 'fonts-noto'.
Ignoring request to alter found versions of bug #954948 to the same values 
previously set
Ignoring request to alter fixed versions of bug #954948 to the same values 
previously set

-- 
954948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954916: another breakage due to LaTeX changes?

[Hilmar Preuße]

Control: reassign -1 src:lgrind
Control: tags -1 + patch

Am 25.03.2020 um 15:57 teilte Joseph Wright mit:
> On 25/03/2020 11:24, Norbert Preining wrote:
>> On Wed, 25 Mar 2020, Joseph Wright wrote:


>>> 'normal', i.e. moving the \begin{document} line, but I'm not sure if
>>> that is
>>> an acceptable fix.
>>
>> Can you send a patch?
>
> See attached
> 
Reassign. patch is reverted, needs to be applied using patch -R .

Hilmar
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#954916: another breakage due to LaTeX changes?

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:lgrind
Bug #954916 [src:lgrind,src:texlive-base] lgrind: FTBFS with current texlive
Bug reassigned from package 'src:lgrind,src:texlive-base' to 'src:lgrind'.
No longer marked as found in versions texlive-base/2020.20200313-1, 
lgrind/3.67-3.1, texlive-base/3.67-3.1, and lgrind/2020.20200313-1.
Ignoring request to alter fixed versions of bug #954916 to the same values 
previously set
> tags -1 + patch
Bug #954916 [src:lgrind] lgrind: FTBFS with current texlive
Added tag(s) patch.

-- 
954916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954912: marked as done (Please switch to gupnp/gssdp 1.2)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 17:34:50 +
with message-id 
and subject line Bug#954912: fixed in librm 2.1.2-3
has caused the Debian Bug report #954912,
regarding Please switch to gupnp/gssdp 1.2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: librm
Version: 2.1.2-2
Severity: serious
Tags: patch

Hello,

Could you please switch the build-dependencies to gupnp/gssdp 1.2
instead of 1.0?

We are currently trying to get rid of the version 1.0 librm has
reintroduced a reverse-dependencies against that old version.

Kind regards
Laurent Bigonville

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
diff -Nru librm-2.1.2/debian/control librm-2.1.2/debian/control
--- librm-2.1.2/debian/control  2020-02-04 22:47:40.0 +0100
+++ librm-2.1.2/debian/control  2020-03-25 08:54:31.0 +0100
@@ -13,8 +13,8 @@
  libspandsp-dev,
  libjson-glib-dev,
  libsndfile1-dev,
- libgupnp-1.0-dev,
- libgssdp-1.0-dev,
+ libgupnp-1.2-dev,
+ libgssdp-1.2-dev,
  libcapi20-dev,
  libgstreamer1.0-dev,
  libgstreamer-plugins-base1.0-dev,
--- End Message ---
--- Begin Message ---
Source: librm
Source-Version: 2.1.2-3
Done: Hilko Bengen 

We believe that the bug you reported is fixed in the latest version of
librm, 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.
Hilko Bengen  (supplier of updated librm 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, 25 Mar 2020 18:20:47 +0100
Source: librm
Architecture: source
Version: 2.1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Closes: 954912
Changes:
 librm (2.1.2-3) unstable; urgency=medium
 .
   * Bump gupnp, gssdp build-dependencies (Closes: #954912)
Checksums-Sha1:
 f1be0513adc4e1f78b7db831e196ed18ac06255a 2185 librm_2.1.2-3.dsc
 858d5a6c407f09606fba6d0b9e603277007932a3 2228 librm_2.1.2-3.debian.tar.xz
 850bae2b5d537c07a1ed412e2ed138288cd0a2a6 5311 librm_2.1.2-3_source.buildinfo
Checksums-Sha256:
 1a6b56fb4d8e62f478bf04b15c347caaf579d9544630485539aac5495f8519d4 2185 
librm_2.1.2-3.dsc
 1bd73de82c296f2f1ef835bb6c0dbd1a7fe56ec1fab869566458f7fe0a215e09 2228 
librm_2.1.2-3.debian.tar.xz
 f191f4f76257494da3a8c52089635942634dbf8e328442c6dd0ac2c2d9cd18bd 5311 
librm_2.1.2-3_source.buildinfo
Files:
 27625d28e2db471e5e6b9071a433edde 2185 libs optional librm_2.1.2-3.dsc
 14323d40392f38ac3566fef3018a7d80 2228 libs optional librm_2.1.2-3.debian.tar.xz
 6c3987ba0920feda59186d56ec5c224a 5311 libs optional 
librm_2.1.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAl57k+ASHGJlbmdlbkBk
ZWJpYW4ub3JnAAoJEHW3EGNcITp+7V0P/2Wz54ewRcVgZ0TpOgr3KLYwEgV2aOOx
bIylq8FDTSS3mG1aQNuq5kxUuLrT83rmpIjs8GVqlgyD1KlZkMy2YITFIAH+nJPi
r0k3tvJL2NN4JEykLyqJN8jXbRJDb+cFZiFooq4W5+6yU/VimojcKYP0NqFZJXic
29WCdEPFOJzboHFFXj8hf0/Jl/iybrCBgLboo0sfs/sl3sW4VtvI8deMG+C1fVTU
7G9s1iDc/qolSRln7jo1ACksGM6ItHvQ1tJ4tOfF9j4rtwQwjP63sk2oqxnxY0mY
RqMd0Mr7HrE1JnTHlJBlj3gOyZUoy3yAfZ63Eg2KI94fBQoLlf2ggPFNcjg4toTc
u5bGCvFgsnVi0YPAXQmdU+32sv6huaugxW7yNmxbogf1FqZm8kqf2MDRrMZlhKRG
9UcER3+C2rUxYQn73btIFIsah4H4+k78mmbmooSHlJkOXK+bAAH5+EU8QZlQ92KT
don+xj53ATRkOsJebUcMErChPD+rD/5FgdBaz9k8xptNWTON68uc4F6ddFdw5hrv
NsjeJRpwUaxBJaMDNhOVDQfdf/g7LxgQA5cdxhC1zdoqpD6nk3MoiGuEZB9TDjeL
KeiIolYzyRNjtBQ8tP8qmNuJBO4w/F2GLo60UcIHhsy1N21vTV/nhoCBzeisM/0R
VTngiGIMsatJ
=Ehcw
-END PGP SIGNATURE End Message ---

Bug#954461: Autopkgtest failure due to use of py3versions -i

[eamanu]

Hi,

I attach a NMU patch. Please consider apply it.

Thanks!

Cheers,

-- 
Emmanuel Arias
@eamanu
yaerobi.com
From 7bb9a35414b61d9392aa5673f63b538b96b7a4cb Mon Sep 17 00:00:00 2001
From: Emmanuel Arias 
Date: Wed, 25 Mar 2020 14:11:33 -0300
Subject: [PATCH] d/tests/smoke-python3: fix autopkgtest regression. Use
 pyversions -s to test all suported versions

---
 debian/changelog   | 8 
 debian/tests/control   | 3 ++-
 debian/tests/smoke-python3 | 2 +-
 3 files changed, 11 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 20ed205..e76bb46 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+editorconfig-core-py (0.12.2-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/tests/smoke-python3: fix autopkgtest regression.
+Use pyversions -s to test all suported versions (Closes: #954461).
+
+ -- Emmanuel Arias   Wed, 25 Mar 2020 14:11:42 -0300
+
 editorconfig-core-py (0.12.2-2) unstable; urgency=medium
 
   [ Ben Finney ]
diff --git a/debian/tests/control b/debian/tests/control
index 2a82b68..53a15a4 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -5,7 +5,8 @@
 Tests: smoke-python3
 Depends:
 python3-pkg-resources,
-python3-editorconfig
+python3-editorconfig,
+python3-all
 
 
 # Local variables:
diff --git a/debian/tests/smoke-python3 b/debian/tests/smoke-python3
index e1767e1..3b3f0da 100755
--- a/debian/tests/smoke-python3
+++ b/debian/tests/smoke-python3
@@ -24,7 +24,7 @@ for mod in ${MODULE_NAMES[@]} ; do
 test_opts="$test_opts --module=$mod"
 done
 
-for py in $(py3versions -i) ; do
+for py in $(py3versions -s) ; do
 printf "Python command: %s\n" $py
 $py debian/tests/smoke_test.py $test_opts
 printf "\n"
-- 
2.25.1



0xFA9DEC5DE11C63F1.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#954915: [libc6] upgrade fail: A copy of the C library was found in an unexpected directory

[Stephan Skrodzki]

On Wed, 25 Mar 2020 10:54:22 +0100 =?utf-8?B?SsO2cmc=?= Sommer
 wrote:
> 
> A quick and dirty workaround is:
> 
> ```
> # egrep '/(ld|lib(d|c|m|pthread|rt|dl))-2.*.so' $I/libc6:amd64.list |sed 
> 's,^,/usr,' |tee -a $I/libc6:amd64.list
> /usr/lib/x86_64-linux-gnu/ld-2.30.so
> /usr/lib/x86_64-linux-gnu/libc-2.30.so
> /usr/lib/x86_64-linux-gnu/libdl-2.30.so
> /usr/lib/x86_64-linux-gnu/libm-2.30.so
> /usr/lib/x86_64-linux-gnu/libpthread-2.30.so
> /usr/lib/x86_64-linux-gnu/librt-2.30.so
> # dpkg --unpack $A/libc6_2.30-3_amd64.deb
> (Lese Datenbank ... 452795 Dateien und Verzeichnisse sind derzeit 
> installiert.)
> Vorbereitung zum Entpacken von .../libc6_2.30-3_amd64.deb ...
> libc6:i386 (2.30-2) wird de-konfiguriert ...
> Entpacken von libc6:amd64 (2.30-3) über (2.30-2) ...

Hmm... strange, why does this not work for me? Although libc6:amd64.list
is expanded with these lines, dkpg --unpack still fails with the same
error message from the bug report...

Bug#936561: freshen: Python2 removal in sid/bullseye

[Boyuan Yang]

Hi Federico,

在 2020-03-24星期二的 22:32 +，Federico Ceratto写道：
> On Tue, Mar 24, 2020 at 2:54 PM Boyuan Yang  wrote:
> > Hi Federico,
> > 
> > I believe your package is a candidate for removal due to upstream
> > inactivity
> > and that the package received no upload in the last 9 years. Besides, the
> > python2 removal is really approaching.
> > 
> > I will submit a removal bug within 7 days to have this package removed. If
> > you
> > have any doubts, please let me know immediately.
> 
> Hello Bouyan and thank you for the ping.
> I was expecting the package to be autoremoved sooner or later.
> Please go ahead with the removal and thank you!

The removal actually won't happen unless someone takes care of it. I will
proceed with the removal. Thanks!

-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part

Bug#954130: marked as done (libxmlada build depends on unicode-data (< 13~) but 13.0.0-2 is to be installed)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 16:49:41 +
with message-id 
and subject line Bug#954130: fixed in libxmlada 19-3
has caused the Debian Bug report #954130,
regarding libxmlada build depends on unicode-data (< 13~) but 13.0.0-2 is to be 
installed
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.)


-- 
954130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxmlada
Version: 19-2
Severity: serious
Tags: ftbfs

The following packages have unmet dependencies:
 builddeps:libxmlada : Depends: unicode-data (< 13~) but 13.0.0-2 is to be 
installed
--- End Message ---
--- Begin Message ---
Source: libxmlada
Source-Version: 19-3
Done: Nicolas Boulenguez 

We believe that the bug you reported is fixed in the latest version of
libxmlada, 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.
Nicolas Boulenguez  (supplier of updated libxmlada 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, 25 Mar 2020 16:16:24 +0100
Source: libxmlada
Architecture: source
Version: 19-3
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Brenta 
Changed-By: Nicolas Boulenguez 
Closes: 954130
Changes:
 libxmlada (19-3) unstable; urgency=medium
 .
   * Update for unicode 13. Closes: #954130.
 The changes affect niche packages, so I am keeping the ALI version.
   * Move gnat and unicode-data from Build-Depends to Build-Depends-Arch.
Checksums-Sha1:
 664c32c6019e25afed2c38f2ac00bb159c92c27a 2934 libxmlada_19-3.dsc
 acc4122fb37acb74455b09dcaacff17108276919 14276 libxmlada_19-3.debian.tar.xz
Checksums-Sha256:
 6c908153867686a4943dc7268c7ed64d1ccf4c7f3d2056438456e6ffee83c774 2934 
libxmlada_19-3.dsc
 8d176837ca0e689212b94fda8f0051d17af99f3d92cc622fb8428101737942d6 14276 
libxmlada_19-3.debian.tar.xz
Files:
 687d6d52bdb63f5a247b0c408efc1469 2934 libdevel optional libxmlada_19-3.dsc
 06373c1525f80f0ebf9a9ed430ee5acc 14276 libdevel optional 
libxmlada_19-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAl57iDsTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jZATD/4/+xEqzziUWuaRpSBS6AH1pRtP6PWg
bBgnIoyxMAalZsRElQY5l5P95kmjmHw94vspbVH/WBI9GrH+4DNBR4V8K4x46jLB
MCZbj5BNoogIp7ijpBd1jJOESSybtskm8/Wlh/wU2w7Db10SUYxNUFUekrBCMiRg
sIrfkZLL2YfwFc2CV+wTzlL/7nOAkCT6hnzsQkZm0buWn87IVcdFy5nPtco8Y11s
wf+Ql6yUXKDNS5DA2+6ihhrkdug8Z8RmI4DnyNAPDUVNsUsp2xHP6bgstgV8dSTC
BhAvB/7kDiqZWpabOPU5Y+sVRRQR4EbdRSjLdw0Dhpy01oLtUnqeOmRlSi2cRgpu
YC9huZNuRaMAbxMO0uYBNI7Gvz/gBQIaPboo8vYVyc2A7wJB9FknqK65/ioriE94
otVizK0DCY7wdttNG3wWv1xZ8GUTPUkLUAKWGI0xa+MF3qtrp2MOS4qu+71n0vWK
5y9CnC6XsFJJuV+oKLQHIArM0mXtxrIobnJX6PRC5MelsJYnghJGBSo3fh7qUM0v
MbFRxdjQ4WhDbAboklsW7SQo2uXchAr1WXJwfYOa98mL3IzP0Z3lgFwTIZgpNCvh
A+VJrI3T2YHV5f6OiPS99KGMM9PDBYzdPVER5Mk3YumC7kQPN/3JKOCinw2MMOdx
ktwjZL7zIdOLVA==
=x9b3
-END PGP SIGNATURE End Message ---

Processed: Re: Broken package in testing repository

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #951634 [gummi] gummi: request to bump gummi package from development to 
release build
Severity set to 'serious' from 'normal'

-- 
951634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954940: marked as done (arcp: d/copyright: needs copyright years for the upstream source)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 16:19:17 +
with message-id 
and subject line Bug#954940: fixed in arcp 0.2.1-3
has caused the Debian Bug report #954940,
regarding arcp: d/copyright: needs copyright years for the upstream 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.)


-- 
954940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: arcp
Version: 0.2.1-1
Severity: serious
Justification: Policy 2.3, 4.5, 12.5

Hello,

During review in NEW I noticed this copyright claim is invalid because
there is no year given:

Files: *
Copyright: Stian Soiland-Reyes 
License: Apache-2.0

(I ACCEPTed from NEW because Apache 2.0 does not require we document all
copyright claims, but Policy does.)

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: arcp
Source-Version: 0.2.1-3
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
arcp, 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.
Andreas Tille  (supplier of updated arcp 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, 25 Mar 2020 16:53:51 +0100
Source: arcp
Architecture: source
Version: 0.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 954940
Changes:
 arcp (0.2.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Add copyright years for the upstream source
 Closes: #954940
Checksums-Sha1:
 e6bfc70a816ba4281f909f87d5023ac38edb 1988 arcp_0.2.1-3.dsc
 dc446903a4e4c97cd41a8370b8f585e8f43fda14 2548 arcp_0.2.1-3.debian.tar.xz
 01ee2382c0f8e85231ce30f80928d8599791849b 6142 arcp_0.2.1-3_amd64.buildinfo
Checksums-Sha256:
 7ed36e1909e99b056aa9f5bc8862dfd6e851bfa3e35b575e5e7e526f9c0b5941 1988 
arcp_0.2.1-3.dsc
 73119877339d15d1d91c1c159b58d2647b94c5949d082b0b42364397953fb455 2548 
arcp_0.2.1-3.debian.tar.xz
 97d65f635388929bcd755e49e7fd26fcd35fe60368f46b3dfe5fc9068b1bd5ca 6142 
arcp_0.2.1-3_amd64.buildinfo
Files:
 519c1a9dc49594a76ad9160680f7277d 1988 python optional arcp_0.2.1-3.dsc
 76b6bf5458503e5b8810c03d1c073eaf 2548 python optional 
arcp_0.2.1-3.debian.tar.xz
 a0f63619dc501062a600d5fc6992d2a8 6142 python optional 
arcp_0.2.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl57f2sRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHcNxAAgeru8y2p69/AMXlozncO/EdCAgVNC6I7
z5+Pxk4+VH3B1ZYPy4x1X4FeO1Ict8Zay8tUDjhOX8J1Y4SJh9jN1iHlr+1u8QyW
74AyXgsrBKZfnYVNxiHcE+sYGPE9POUbZ/J6R/F63aO0zzeS8tDtoC8ebocZrvM8
Trpai55qXV3rUNH/SAplEIF3/Nmoe50pytL6GGM2sWZ+h4IRVK2jGOyZdcD4B0oM
HAGgVkZKCl+71HsunKJleuf4YDyl6Z7Nm9KNVTqggiEu6RtIytNDTLPvdboGvtFa
8R6kKkTN8YyQjaIExNIMH1+j4PYYpvd8VXQyhgjyPIa+2xpRsFCxUCy7gYdqeEqE
1+YNe5SJDjbijcDgrOQySg+lDoBA0L7IK4IR2C0ZNw+U5L4UJbEuC+jOF464stMv
HmrAkS5AVkS/p6CC4vgM3usUbllsI8xzG+E/nFTq+3NkQJ2GyGeZEstXgMueH3nH
nVQBxQDwhQ9fkltQW+n+AkVMffKN3ywmRIvFyWPakqd1KfavZdMluK/TB9Ilv3BY
Vh5HnqdXD7VRKRcYgVpN520pWo0GeR47as7XopirCM29tyg1svTIvO4ozUc6p2Ex
b1qKNtTSdEysXvevxx0ebo91DQTz7UG8OVZQJfkMyyi/vegSqGzVcpcgrB5Er0Me
YKcEd7s8aOM=
=WC0u
-END PGP SIGNATURE End Message ---

Bug#954897: pydxcluster: should this package be removed?

[Christoph Berg]

Re: Sandro Tosi 2020-03-25 
<158509215087.18239.15325100274815623896.report...@zion.matrix.int>
> i believe this package should be removed:

+1 from me.

Christoph

Bug#954940: arcp: d/copyright: needs copyright years for the upstream source

[Sean Whitton]

Source: arcp
Version: 0.2.1-1
Severity: serious
Justification: Policy 2.3, 4.5, 12.5

Hello,

During review in NEW I noticed this copyright claim is invalid because
there is no year given:

Files: *
Copyright: Stian Soiland-Reyes 
License: Apache-2.0

(I ACCEPTed from NEW because Apache 2.0 does not require we document all
copyright claims, but Policy does.)

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#953069: marked as done (libgnatcoll-db: FTBFS on mipsel with assembler message: branch out of range)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 15:37:39 +
with message-id 
and subject line Bug#953069: fixed in libgnatcoll-db 19.2-3
has caused the Debian Bug report #953069,
regarding libgnatcoll-db: FTBFS on mipsel with assembler message: branch out of 
range
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.)


-- 
953069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgnatcoll-db
Version: 19.2-2
Severity: normal

The relevant lines are:

xref/gnatcoll-xref.adb: In function ‘GNATCOLL.XREF’:
xref/gnatcoll-xref.adb:40:1: note: variable tracking size limit exceeded with 
‘-fvar-tracking-assignments’, retrying without
Assembler messages:
678119: Error: branch out of range
--- End Message ---
--- Begin Message ---
Source: libgnatcoll-db
Source-Version: 19.2-3
Done: Nicolas Boulenguez 

We believe that the bug you reported is fixed in the latest version of
libgnatcoll-db, 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.
Nicolas Boulenguez  (supplier of updated libgnatcoll-db 
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, 25 Mar 2020 15:40:52 +0100
Source: libgnatcoll-db
Architecture: source
Version: 19.2-3
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Boulenguez 
Changed-By: Nicolas Boulenguez 
Closes: 953069
Changes:
 libgnatcoll-db (19.2-3) unstable; urgency=medium
 .
   [ Aurelien Jarno  ]
   * Compile with mixgot option on mipsel. Closes: #953069.
Checksums-Sha1:
 b58cbc9d9ff961d3b1ea29fac7561879db2063c8 2548 libgnatcoll-db_19.2-3.dsc
 758cddea6c14c0ed7405e2e30d953bebbc4029ae 13316 
libgnatcoll-db_19.2-3.debian.tar.xz
Checksums-Sha256:
 26222e795511c013e6967818ce68091af2a518561aa03d06a249ef87e8671f15 2548 
libgnatcoll-db_19.2-3.dsc
 6e537fd67273e084f5f95d64ad74d84bda3d0a923ea07706b93267d74365f7af 13316 
libgnatcoll-db_19.2-3.debian.tar.xz
Files:
 afdd8f6c5a6fbc8a6cc24c61743c3168 2548 misc optional libgnatcoll-db_19.2-3.dsc
 7e45f0a0f21000af809815942fe506e7 13316 misc optional 
libgnatcoll-db_19.2-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAl57cR0THG5pY29sYXNA
ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jVpoD/95LcP+LAsFd5LKcJwLL340wQSx3//6
fEM/g2Emba9WVY2chDkEMPt4Etv7Iq11A/fqtIZ3o+3t4XmT9XzZ8hApOr8ea3un
/K7M4wH6pJo5vipeYtFyO+WYwy3dpgrAXVYsv82MKOPgCve91G23yKgdAorFQLo5
8c42X+fcTeVQSpN+EYHkSDT7JY4/Br12LdBMI/xJk9erYNamBwP/ABkjhJAmLG08
WsNB8Uk+JYhY7KmfurrMPjrpnWZd60nRqxnxw9xNyQCWWbA7UOSiu7AbhzLsoxhM
hvAwHxUVGBpwVYLPSM1PDBcrYBVlAcz2uxz1BDmP298+vmrpQZ22L+4yhuN3GUlK
h2mUBUo+hz8XGtOGH/nKOjJNqhz8ORODcjQyE7OGzcMzaLslqknr/TcR+S+b99Fc
3palfR8spJdkkpzUS4tbjwCPUjzms111kmPjiCdQmcHXCD89ubInOUc/svXQ2NV/
ft42PbUL5+3ivN1jq0CHArN16/zwc2A82exceYq1xz20t8HmOL5WjbbVkQNVoKKn
KDJNtzfKGC2XeYj6TTXWbTuzkEqXZh9i89Zyg9D+uq+uLOgii9AHPLoCHloWGvDG
HQW5LZHLeCdOuxSuMeE/4jwqv9yg/7YagGxffb7K7dU03ZNNYVdk3BDRzwFQl8jw
tnfDCQjaBhnWiA==
=WV1q
-END PGP SIGNATURE End Message ---

Bug#938327: marked as done (rabbitvcs: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 15:08:25 +
with message-id 
and subject line Bug#938327: fixed in rabbitvcs 0.18-1
has caused the Debian Bug report #938327,
regarding rabbitvcs: 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.)


-- 
938327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rabbitvcs
Version: 0.17.1-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:rabbitvcs

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: rabbitvcs
Source-Version: 0.18-1
Done: Ritesh Raj Sarraf 

We believe that the bug you reported is fixed in the latest version of
rabbitvcs, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 938...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated rabbitvcs 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, 25 Mar 2020 19:12:00 +0530
Source: rabbitvcs
Architecture: source
Version: 0.18-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Ritesh Raj Sarraf 
Closes: 938327
Changes:
 rabbitvcs (0.18-1) unstable; urgency=medium
 .
   * New upstream version 0.18
   * Switch to python 3 (Closes: #938327)
   * Specify pybuild build system
   * Disable auto test invcation, temporarily
   * Drop patch 99_setyup.py.patch
   * Update plugin path for Nautilus
   * Update debian/control
Checksums-Sha1:
 c7b111500383089d9d847c8979bc1dc5f70357f6 2305 rabbitvcs_0.18-1.dsc
 47dcf99ffa767015c3400ba942e900f9a3db9f1b 1677574 rabbitvcs_0.18.orig.tar.gz
 4f4acbe4dcd921aadfe3545e049e8d84c47e3d47 6040 rabbitvcs_0.18-1.debian.tar.xz
Checksums-Sha256:
 7f2fd22bd5a9fcdee8a81d69c935bb5c13b88dea11cab613bd03105d190c6205 2305 
rabbitvcs_0.18-1.dsc
 

Bug#954916: another breakage due to LaTeX changes?

[Joseph Wright]

On 25/03/2020 11:24, Norbert Preining wrote:

On Wed, 25 Mar 2020, Joseph Wright wrote:

The structure of the .dtx is ... unusual. It's got the \begin{document} in


Yes, this is what I saw, too, but it was working before ;-)


'normal', i.e. moving the \begin{document} line, but I'm not sure if that is
an acceptable fix.


Can you send a patch?

Thanks

Best

Norbert


See attached

Joseph
--- lgrind.dtx  2020-03-25 14:56:20.117715900 +
+++ lgrind-orig.dtx 2020-03-25 14:55:18.313276900 +
@@ -20,17 +20,16 @@
 %
 %<*dtx>
 \ProvidesFile{lgrind.dtx}
-  [2020/03/25 v3.68 LGrind environment and supporting stuff]
+  [2002/01/28 v3.67 LGrind environment and supporting stuff]
 %
 %\NeedsTeXFormat{LaTeX2e}[1996/06/01]
 %\ProvidesPackage{lgrind}
-%  [2020/03/25 v3.68 LGrind environment and supporting stuff]
+%  [2002/01/28 v3.67 LGrind environment and supporting stuff]
 %<*driver>
 \NeedsTeXFormat{LaTeX2e}[1996/06/01]
 \documentclass{ltxdoc}
 \CodelineIndex
 \RecordChanges
-\begin{document}
 \DocInput{lgrind.dtx}
 \end{document}
 %
@@ -41,6 +40,7 @@
 % \frenchspacing
 % 
 % \GetFileInfo{lgrind.dtx}
+% \begin{document}
 % \title{The \LG{} package\thanks{This file
 % has version number \fileversion, last
 % revised \filedate.}}

Bug#950382: marked as done (apertium-mk-en FTBFS with apertium 3.6.1)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 14:50:09 +
with message-id 
and subject line Bug#950382: fixed in apertium-mk-en 0.1.1~r57554-3
has caused the Debian Bug report #950382,
regarding apertium-mk-en FTBFS with apertium 3.6.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.)


-- 
950382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-mk-en
Version: 0.1.1~r57554-2
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-mk-en.html

...
make -j16
make[1]: Entering directory '/build/1st/apertium-mk-en-0.1.1~r57554'
apertium-validate-dictionary apertium-mk-en.mk.dix
apertium-validate-dictionary apertium-mk-en.en.dix
if [ ! -d .deps ]; then mkdir .deps; fi
apertium-validate-dictionary apertium-mk-en.en.dix
apertium-validate-transfer apertium-mk-en.mk-en.t1x
xsltproc lexchoicebil.xsl apertium-mk-en.mk-en.dix > 
.deps/apertium-mk-en.mk-en.dix
apertium-validate-interchunk apertium-mk-en.mk-en.t2x
apertium-validate-postchunk apertium-mk-en.mk-en.t3x
cg-comp apertium-mk-en.mk-en.rlx mk-en.rlx.bin
cg-comp apertium-mk-en.mk-en.lex mk-en.lex.bin
apertium-preprocess-transfer apertium-mk-en.mk-en.t2x mk-en.t2x.bin
apertium-validate-dictionary apertium-mk-en.mk-en.alpha.dix
apertium-preprocess-transfer apertium-mk-en.mk-en.t3x mk-en.t3x.bin
Sections: 1, Rules: 18, Sets: 45, Tags: 65
apertium-preprocess-transfer apertium-mk-en.mk-en.t1x mk-en.t1x.bin
apertium-validate-dictionary apertium-mk-en.post-en.dix
lt-comp rl apertium-mk-en.mk-en.alpha.dix mk-en.alpha.bin
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 103 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 106 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 109 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 124 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 127 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 159 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 192 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 197 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 199 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 200 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 203 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 212 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 219 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 221 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 226 after 
previous rule!
apertium-validate-modes modes.xml
m...@inconditionapertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 
252 after previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 307 after 
previous rule!
al 5 65
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 463 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 465 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 475 after 
previous rule!
apertium-mk-en.mk-en.rlx: Warning: Expected closing ; on line 479 after 
previous rule!
Sections: 2, Rules: 108, Sets: 139, Tags: 211
15 rules cannot be skipped by index.
Warning (5400): assignment to 'sl' side has no effect.
apertium-gen-modes modes.xml
lt-comp lr apertium-mk-en.post-en.dix mk-en.autopgen.bin
main@standard 39 82
cp *.mode modes/
cp: cannot stat '*.mode': No such file or directory
make[1]: *** [Makefile:704: modes/mk-en.mode] Error 1
--- End Message ---
--- Begin Message ---
Source: apertium-mk-en
Source-Version: 0.1.1~r57554-3
Done: Kartik Mistry 

We believe that the bug you reported is fixed in the latest version of
apertium-mk-en, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 950...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated apertium-mk-en package)

(This message was generated 

Bug#954480: python-tinyrpc: Autopkgtest failure due to use of py3versions -i

[eamanu]

Hi,

I attach a NMU patch. Please, consider apply it.

Thanks!
Cheers,

-- 
Emmanuel Arias
@eamanu
yaerobi.com
From 12441b71f337e965c3304ab6700f84d455c6dadc Mon Sep 17 00:00:00 2001
From: Emmanuel Arias 
Date: Wed, 25 Mar 2020 11:03:55 -0300
Subject: [PATCH] d/tests/smoke-python3: fix autopkgtest regression. Use
 pyversions -s to test all suported versions

---
 debian/changelog   | 8 
 debian/tests/control   | 3 ++-
 debian/tests/smoke-python3 | 2 +-
 3 files changed, 11 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 4a1a688..43f1118 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+python-tinyrpc (0.6-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/tests/smoke-python3: fix autopkgtest regression.
+Use pyversions -s to test all suported versions (Closes: #954480).
+
+ -- Emmanuel Arias   Wed, 25 Mar 2020 11:04:01 -0300
+
 python-tinyrpc (0.6-3) unstable; urgency=medium
 
   * Remove obsolete smoke test program for Python 2.
diff --git a/debian/tests/control b/debian/tests/control
index 4e5c4ce..ed0e813 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -5,7 +5,8 @@
 Tests: smoke-python3
 Depends:
 python3-pkg-resources,
-python3-tinyrpc
+python3-tinyrpc,
+python3-all
 
 
 # Local variables:
diff --git a/debian/tests/smoke-python3 b/debian/tests/smoke-python3
index 1ad04f0..f067ca7 100755
--- a/debian/tests/smoke-python3
+++ b/debian/tests/smoke-python3
@@ -24,7 +24,7 @@ for mod in ${MODULE_NAMES[@]} ; do
 test_opts="$test_opts --module=$mod"
 done
 
-for py in $(py3versions -i) ; do
+for py in $(py3versions -s) ; do
 printf "Python command: %s\n" $py
 $py debian/tests/smoke_test.py $test_opts
 printf "\n"
-- 
2.25.1



0xFA9DEC5DE11C63F1.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#953069: libgnatcoll-db: FTBFS on mipsel with assembler message: branch out of range

[Aurelien Jarno]

control: tag -1 + patch

On 2020-03-25 09:51, Aurelien Jarno wrote:
> Hi,
> 
> On 2020-03-12 13:55, Emilio Pozuelo Monfort wrote:
> > Control: severity -1 serious
> > 
> > On Wed, 4 Mar 2020 01:53:25 +0100 Nicolas Boulenguez  
> > wrote:
> > > Source: libgnatcoll-db
> > > Version: 19.2-2
> > > Severity: normal
> > > 
> > > The relevant lines are:
> > > 
> > > xref/gnatcoll-xref.adb: In function ‘GNATCOLL.XREF’:
> > > xref/gnatcoll-xref.adb:40:1: note: variable tracking size limit exceeded 
> > > with ‘-fvar-tracking-assignments’, retrying without
> > > Assembler messages:
> > > 678119: Error: branch out of range
> > 
> > This package has old binaries in mipsel, so this failure is RC as it 
> > prevents
> > the package from migrating to testing.
>  
> I have just got aware of this bug as it indirectly prevents gcc-8
> removal and makes the GCC maintainer angry. In the future don't hesitate
> to Cc: the debian-m...@lists.debian.org mailing list so that porters can
> be aware of the issue.
> 
> My knowledge of ADA is very limited, so I am not sure I fully understood
> the problem. However please find below a first workaround using the
> -mxgot option to increase the size of the GOT and allow bigger jumps.

Hmm I didn't test the latest version of my patch. It happens that the
DEB_CFLAGS_MAINT_APPEND variable has to be set before the include
/usr/share/dpkg/buildflags.mk. Please find below an updated patch:

--- libgnatcoll-db-19.2/debian/rules2019-12-17 11:41:57.0 +
+++ libgnatcoll-db-19.2/debian/rules2020-03-25 08:41:05.0 +
@@ -23,6 +23,13 @@
 DEB_BUILD_MAINT_OPTIONS := hardening=+all
 DEB_LDFLAGS_MAINT_APPEND := -Wl,--no-undefined \
   -Wl,--no-copy-dt-needed-entries -Wl,--no-allow-shlib-undefined
+
+# On mipsel gnatcoll-xref.adb generates long jump that do not fit in
+# standard branch instructions. Use the mxgot option to workaround that.
+ifeq ($(DEB_HOST_ARCH),mipsel)
+DEB_CFLAGS_MAINT_APPEND := -mxgot
+endif
+
 include /usr/share/dpkg/buildflags.mk
 include /usr/share/ada/debian_packaging-$(GNAT_VERSION).mk

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 954480 + patch
Bug #954480 [src:python-tinyrpc] src:python-tinyrpc: Autopkgtest failure due to 
use of py3versions -i
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: libgnatcoll-db: FTBFS on mipsel with assembler message: branch out of range

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #953069 [src:libgnatcoll-db] libgnatcoll-db: FTBFS on mipsel with assembler 
message: branch out of range
Added tag(s) patch.

-- 
953069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954566: marked as done (cura-engine: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 14:58:25 +0100
with message-id <20200325135825.gd1590...@msg.df7cb.de>
and subject line Re: [3dprinter-general] Bug#954566: cura-engine: FTBFS: 
dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 
returned exit code 2
has caused the Debian Bug report #954566,
regarding cura-engine: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && 
make -j4 test ARGS\+=-j4 returned exit code 2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cura-engine
Version: 1:4.5.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process -j4
> Test project /<>/obj-x86_64-linux-gnu
>   Start  1: BuildTests
>   Start  2: GCodeExportTest
>   Start  3: InfillTest
>   Start  4: LayerPlanTest
>  1/21 Test  #4: LayerPlanTest ***Exception: SegFault  
> 0.00 sec
> 
>   Start  5: MergeInfillLinesTest
>  2/21 Test  #5: MergeInfillLinesTest .***Exception: SegFault  
> 0.00 sec
> 
>   Start  6: TimeEstimateCalculatorTest
>  3/21 Test  #6: TimeEstimateCalculatorTest ...***Exception: SegFault  
> 0.00 sec
> 
>   Start  7: SlicePhaseTest
>  4/21 Test  #7: SlicePhaseTest ...***Exception: SegFault  
> 0.00 sec
> 
>   Start  8: SettingsTest
>  5/21 Test  #8: SettingsTest .***Exception: SegFault  
> 0.00 sec
> 
>   Start  9: ArcusCommunicationTest
>  6/21 Test  #9: ArcusCommunicationTest ...***Exception: SegFault  
> 0.00 sec
> 
>   Start 10: ArcusCommunicationPrivateTest
>  7/21 Test  #2: GCodeExportTest ..***Exception: SegFault  
> 0.03 sec
> 
>   Start 11: AABBTest
>  8/21 Test #11: AABBTest .   Passed0.00 sec
>   Start 12: AABB3DTest
>  9/21 Test #12: AABB3DTest ...   Passed0.00 sec
>   Start 13: IntPointTest
> 10/21 Test #13: IntPointTest .   Passed0.00 sec
>   Start 14: LinearAlg2DTest
> 11/21 Test  #3: InfillTest ...***Exception: SegFault  
> 0.04 sec
> 
>   Start 15: MinimumSpanningTreeTest
> 12/21 Test #14: LinearAlg2DTest ..   Passed0.00 sec
>   Start 16: PolygonConnectorTest
> 13/21 Test #15: MinimumSpanningTreeTest ..   Passed0.00 sec
>   Start 17: PolygonTest
> 14/21 Test #17: PolygonTest ..   Passed0.00 sec
>   Start 18: PolygonUtilsTest
> 15/21 Test #18: PolygonUtilsTest .   Passed0.00 sec
>   Start 19: SparseGridTest
> 16/21 Test #16: PolygonConnectorTest .   Passed0.01 sec
>   Start 20: StringTest
> 17/21 Test #19: SparseGridTest ...   Passed0.00 sec
>   Start 21: UnionFindTest
> 18/21 Test #20: StringTest ...   Passed0.00 sec
> 19/21 Test #21: UnionFindTest    Passed0.00 sec
> 20/21 Test #10: ArcusCommunicationPrivateTest ***Exception: SegFault  
> 0.12 sec
> 
> 21/21 Test  #1: BuildTests ...   Passed0.48 sec
> 
> 57% tests passed, 9 tests failed out of 21
> 
> Total Test time (real) =   0.48 sec
> 
> The following tests FAILED:
> 2 - GCodeExportTest (SEGFAULT)
> 3 - InfillTest (SEGFAULT)
> 4 - LayerPlanTest (SEGFAULT)
> 5 - MergeInfillLinesTest (SEGFAULT)
> 6 - TimeEstimateCalculatorTest (SEGFAULT)
> 7 - SlicePhaseTest (SEGFAULT)
> 8 - SettingsTest (SEGFAULT)
> 9 - ArcusCommunicationTest (SEGFAULT)
>10 - ArcusCommunicationPrivateTest (SEGFAULT)
> Errors while running CTest
> make[1]: *** [Makefile:143: test] Error 8
> make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 
> returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/cura-engine_4.5.0-2_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 

Bug#954915: marked as pending in glibc

[Simon McVittie]

On Wed, 25 Mar 2020 at 13:15:03 +, Aurelien Jarno wrote:
> debian/debhelper.in/libc.preinst, debian/rules.d/debhelper.mk: there is no 
> easy way to check if a file belongs to a package with usrmerge. Just drop all 
> safety checks...  Closes: #954915.

The /usr merge merges /foo with /usr/foo (for some values of foo) and
nothing else, so if you would prefer to keep those checks, you could do
something like this:

if dpkg-query -S "${lib#/usr}" >/dev/null 2>&1 ; then
continue
fi

if dpkg-query -S "/usr${lib#/usr}" >/dev/null 2>&1 ; then
continue
fi

which will in particular treat /usr/lib/whatever as equivalent to
/lib/whatever.

(And the same for the quicker check involving libcfiles - but I don't
understand how or whether that one works, because it seems to be telling
grep to look for ^ and $ as literals rather than as anchors, which seems
wrong to me. But perhaps I'm missing something there.)

smcv

Bug#954915: marked as done ([libc6] upgrade fail: A copy of the C library was found in an unexpected directory)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 13:35:22 +
with message-id 
and subject line Bug#954915: fixed in glibc 2.30-4
has caused the Debian Bug report #954915,
regarding [libc6] upgrade fail: A copy of the C library was found in an 
unexpected directory
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.)


-- 
954915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.30-3

sudo aptitude upgrade just now:

```
Preparing to unpack .../libc6-dev_2.30-3_amd64.deb ...
Unpacking libc6-dev:amd64 (2.30-3) over (2.30-2) ...
Preparing to unpack .../libc-dev-bin_2.30-3_amd64.deb ...
Unpacking libc-dev-bin (2.30-3) over (2.30-2) ...
Preparing to unpack .../libc6-dbg_2.30-3_amd64.deb ...
Unpacking libc6-dbg:amd64 (2.30-3) over (2.30-2) ...
Preparing to unpack .../libc6_2.30-3_amd64.deb ...

A copy of the C library was found in an unexpected directory:
  '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
It is not safe to upgrade the C library in this situation;
please remove that copy of the C library or get it out of
'/usr/lib/x86_64-linux-gnu' and try again.

dpkg: error processing archive /var/cache/apt/archives/libc6_2.30-
3_amd64.deb (--unpack):
 new libc6:amd64 package pre-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.30-3_amd64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
dpkg: dependency problems prevent configuration of libc6-dbg:amd64:
 libc6-dbg:amd64 depends on libc6 (= 2.30-3); however:
  Version of libc6:amd64 on system is 2.30-2.

dpkg: error processing package libc6-dbg:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libc6-dev:amd64:
 libc6-dev:amd64 depends on libc6 (= 2.30-3); however:
  Version of libc6:amd64 on system is 2.30-2.

dpkg: error processing package libc6-dev:amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up libc-dev-bin (2.30-3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.30-2) ...
Errors were encountered while processing:
 libc6-dbg:amd64
 libc6-dev:amd64
```
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.30-4
Done: Aurelien Jarno 

We believe that the bug you reported is fixed in the latest version of
glibc, 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.
Aurelien Jarno  (supplier of updated glibc 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, 25 Mar 2020 13:56:56 +0100
Source: glibc
Architecture: source
Version: 2.30-4
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 954915
Changes:
 glibc (2.30-4) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/debhelper.in/libc.preinst, debian/rules.d/debhelper.mk: there
 is no easy way to check if a file belongs to a package with usrmerge.
 Just drop all safety checks...  Closes: #954915.
   * debian/patches/any/local-tst-system-disable-shell-tests.diff: disable
 tests that rely on a particular shell until a fix is found upstream.
 .
   [ John Paul Adrian Glaubitz ]
   * debian/testsuite-xfail-debian.mk: mark nptl/tst-cond8-static and
 nptl/tst-mutex{,pi}8-static as XFAIL on sparc64.
Checksums-Sha1:
 9270975bdfd83e676bc1efc4c59be0cb966c9c22 8731 glibc_2.30-4.dsc
 3d6d0acbc4a4f998ae95425b53e55bd779c0a35f 843820 glibc_2.30-4.debian.tar.xz
 a4d077fb683b1951b60fa4dc8c21fbad287a1acb 7589 glibc_2.30-4_source.buildinfo
Checksums-Sha256:
 84c8d7c231ba1f683023391f794e9dc39710af1e3ae70b15dee73453cb9b7d9f 8731 
glibc_2.30-4.dsc
 d223a88aff38b11c414b17f8e1be6a0a392115fb5451c7e9f5bf6c12955c4275 843820 
glibc_2.30-4.debian.tar.xz
 28e660a2c6729827e53e86cca11340f7d015711c65db108f3f9808fefaa1370b 7589 
glibc_2.30-4_source.buildinfo
Files:
 930de8f673f1ae03a5f4f1ff8152fec9 8731 libs required glibc_2.30-4.dsc
 

Bug#954933: marked as done (libc6: Not installing package libc6. Problem script.)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 13:35:22 +
with message-id 
and subject line Bug#954915: fixed in glibc 2.30-4
has caused the Debian Bug report #954915,
regarding libc6: Not installing package libc6. Problem script.
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.)


-- 
954915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.30-2
Severity: important

Dear Maintainer,

Only fail this package, and returnet fail:

A copy of the C library was found in an unexpected directory:
  '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
It is not safe to upgrade the C library in this situation;
please remove that copy of the C library or get it out of
'/usr/lib/x86_64-linux-gnu' and try again.

dpkg: error al procesar el archivo 
/var/cache/apt/archives/libc6_2.30-3_amd64.deb (--unpack):
 el subproceso nuevo paquete libc6:amd64 script pre-installation devolvió el 
código de salida de error 1
Se encontraron errores al procesar:
 /var/cache/apt/archives/libc6_2.30-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Others packages is installed, only this package fail.

This package is problem in update. No fail others packages. Only this.

In this moment in the version 2.30-2 of libc6.

Thanks.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/12 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libc6 depends on:
ii  libcrypt1  1:4.4.15-1
ii  libgcc-s1  10-20200324-1

Versions of packages libc6 recommends:
ii  libidn2-0  2.3.0-1

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.73
pn  glibc-doc  
ii  libc-l10n  2.30-3
ii  locales2.30-3

-- debconf information:
* glibc/upgrade: true
  glibc/kernel-too-old:
* libraries/restart-without-asking: true
  glibc/restart-services:
  glibc/disable-screensaver:
  glibc/restart-failed:
  glibc/kernel-not-supported:
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.30-4
Done: Aurelien Jarno 

We believe that the bug you reported is fixed in the latest version of
glibc, 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.
Aurelien Jarno  (supplier of updated glibc 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, 25 Mar 2020 13:56:56 +0100
Source: glibc
Architecture: source
Version: 2.30-4
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 954915
Changes:
 glibc (2.30-4) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/debhelper.in/libc.preinst, debian/rules.d/debhelper.mk: there
 is no easy way to check if a file belongs to a package with usrmerge.
 Just drop all safety checks...  Closes: #954915.
   * debian/patches/any/local-tst-system-disable-shell-tests.diff: disable
 tests that rely on a particular shell until a fix is found upstream.
 .
   [ John Paul Adrian Glaubitz ]
   * debian/testsuite-xfail-debian.mk: mark nptl/tst-cond8-static and
 nptl/tst-mutex{,pi}8-static as XFAIL on sparc64.
Checksums-Sha1:
 9270975bdfd83e676bc1efc4c59be0cb966c9c22 8731 glibc_2.30-4.dsc
 3d6d0acbc4a4f998ae95425b53e55bd779c0a35f 843820 glibc_2.30-4.debian.tar.xz
 a4d077fb683b1951b60fa4dc8c21fbad287a1acb 7589 glibc_2.30-4_source.buildinfo
Checksums-Sha256:
 84c8d7c231ba1f683023391f794e9dc39710af1e3ae70b15dee73453cb9b7d9f 8731 
glibc_2.30-4.dsc
 d223a88aff38b11c414b17f8e1be6a0a392115fb5451c7e9f5bf6c12955c4275 843820 
glibc_2.30-4.debian.tar.xz
 28e660a2c6729827e53e86cca11340f7d015711c65db108f3f9808fefaa1370b 7589 
glibc_2.30-4_source.buildinfo
Files:
 930de8f673f1ae03a5f4f1ff8152fec9 8731 libs required glibc_2.30-4.dsc
 48419cf9436a0c326076375b4cc5a658 843820 libs required 

Bug#938327: Upstream references

[Ritesh Raj Sarraf]

On Tue, 2020-03-24 at 21:42 +0100, Moritz Mühlenhoff wrote:
> On Sun, Dec 15, 2019 at 02:01:30PM +, Jelmer Vernooij wrote:
> 
> > FWIW Upstream is working on Python 3 support here: 
> > https://github.com/rabbitvcs/rabbitvcs/issues/279
> 
> 
> Hi Ritesh,
> 
> this is fixed in 0.18, could you please update the package? rabbitcvs
> is among
> 
> the last handful of packages blocking the pygtk removal at this
> point.

Hi Mortiz,

Yes. I should be able to get this complete soon. Hopefully by this
week.

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


signature.asc
Description: This is a digitally signed message part

Processed: forcibly merging 954915 954933

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 954915 954933
Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in 
an unexpected directory
Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in 
an unexpected directory
Marked as found in versions glibc/2.30-2.
Bug #954933 [libc6] libc6: Not installing package libc6. Problem script.
Severity set to 'serious' from 'important'
Marked as found in versions glibc/2.30-3.
Added tag(s) confirmed and pending.
Merged 954915 954933
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954915
954933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954222: marked as done (src:appdirs: Fails autopkgtest with non-default python3 installed)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 13:19:12 +
with message-id 
and subject line Bug#954222: fixed in appdirs 1.4.3-2.1
has caused the Debian Bug report #954222,
regarding src:appdirs: Fails autopkgtest with non-default python3 installed
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.)


-- 
954222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:appdirs
Version: 1.4.3-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Note: Using the ftbfs tag since it seems to be the closest thing we have
for this.

Appdirs failed a recent autopkgtest and this is one of the blockers for
python3-defaults migration.  It failed because python3.7 was installed
in the chroot and the current autopkgtest doesn't handle that.

Autopkgtests should be run for all supported versions.  The attached
patch should solve it (untested on this package, but I've tested the
approach on others with the same problem).  Despite being in the form of
an NMU diff, I do not plan to NMU now.  If we get to the point where
this is one of a few remaining blockers or if the maintianers ask me to
handle it, then I will.  Please let me know (not cc'ed to the bug, so
either include -submitter or email me directly).

Here's the exact failure:

autopkgtest [09:16:17]: test python3: cp -r test "$AUTOPKGTEST_TMP" && cd 
"$AUTOPKGTEST_TMP" && for py in $(py3versions -vi); do "python$py" -m unittest 
discover -v; done
autopkgtest [09:16:17]: test python3: [---
/usr/bin/python3.7: No module named unittest
autopkgtest [09:16:18]: test python3: ---]
autopkgtest [09:16:18]: test python3:  - - - - - - - - - - results - - - - - - 
- - - -
python3  FAIL non-zero exit status 1

Scott K
diff -Nru appdirs-1.4.3/debian/changelog appdirs-1.4.3/debian/changelog
--- appdirs-1.4.3/debian/changelog  2020-02-26 15:13:19.0 -0500
+++ appdirs-1.4.3/debian/changelog  2020-03-18 15:30:59.0 -0400
@@ -1,3 +1,10 @@
+appdirs (1.4.3-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix autopkgtest to reliably run with multiple python3 versions installed
+
+ -- Scott Kitterman   Wed, 18 Mar 2020 15:30:59 -0400
+
 appdirs (1.4.3-2) unstable; urgency=medium
 
   * Move repository to salsa.debian.org
diff -Nru appdirs-1.4.3/debian/tests/control appdirs-1.4.3/debian/tests/control
--- appdirs-1.4.3/debian/tests/control  2020-02-26 15:06:10.0 -0500
+++ appdirs-1.4.3/debian/tests/control  2020-03-18 15:30:59.0 -0400
@@ -3,7 +3,7 @@
 Restrictions: allow-stderr
 Features: test-name=pypy
 
-Test-Command: cp -r test "$AUTOPKGTEST_TMP" && cd "$AUTOPKGTEST_TMP" && for py 
in $(py3versions -vi); do "python$py" -m unittest discover -v; done
-Depends: python3-appdirs
+Test-Command: cp -r test "$AUTOPKGTEST_TMP" && cd "$AUTOPKGTEST_TMP" && for py 
in $(py3versions -vs); do "python$py" -m unittest discover -v; done
+Depends: python3-all, python3-appdirs
 Restrictions: allow-stderr
 Features: test-name=python3
--- End Message ---
--- Begin Message ---
Source: appdirs
Source-Version: 1.4.3-2.1
Done: Scott Kitterman 

We believe that the bug you reported is fixed in the latest version of
appdirs, 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.
Scott Kitterman  (supplier of updated appdirs 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, 25 Mar 2020 08:38:40 -0400
Source: appdirs
Architecture: source
Version: 1.4.3-2.1
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung 
Changed-By: Scott Kitterman 
Closes: 954222
Changes:
 appdirs (1.4.3-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix autopkgtest to reliably run with multiple python3 versions installed
 (Closes: #954222)
Checksums-Sha1:
 57d24d8466b89a57d5f9f5802a7203cdc3230e20 2082 appdirs_1.4.3-2.1.dsc
 58199f39b33685fb121a6fa5bb4db5152189e636 3312 appdirs_1.4.3-2.1.debian.tar.xz
 

Bug#954915: marked as pending in glibc

[Aurelien Jarno]

Control: tag -1 pending

Hello,

Bug #954915 in glibc 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/glibc-team/glibc/-/commit/49d137c4392cb1144f2313f78f31466aaa169b75


debian/debhelper.in/libc.preinst, debian/rules.d/debhelper.mk: there is no easy 
way to check if a file belongs to a package with usrmerge. Just drop all safety 
checks...  Closes: #954915.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954915

Processed: Bug#954915 marked as pending in glibc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in 
an unexpected directory
Added tag(s) pending.

-- 
954915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954608: marked as done (godot: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 13:04:37 +
with message-id 
and subject line Bug#954608: fixed in godot 3.2-stable-2
has caused the Debian Bug report #954608,
regarding godot: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess 
returned exit status 2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: godot
Version: 3.2-stable-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_clean
>   rm -f debian/debhelper-build-stamp
>   rm -rf debian/.debhelper/
>   rm -f -- debian/godot3.substvars debian/godot3-runner.substvars 
> debian/godot3-server.substvars 
> ./platform/android/java/gradle/wrapper/gradle-wrapper.jar debian/files
>   rm -fr -- debian/godot3/ debian/tmp/ debian/godot3-runner/ 
> debian/godot3-server/
>   find .  \( \( \
>   \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path 
> .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o 
> -type f -a \
>   \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
>-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
>-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
>-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
>   \) -exec rm -f {} + \) -o \
>   \( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) 
> \)
> scons -c
> scons: Reading SConscript files ...
> Automatically detected platform: x11
> Enabling ALSA
> Enabling PulseAudio
> YASM is necessary for WebM SIMD optimizations.
> WebM SIMD optimizations are disabled. Check if your CPU architecture, CPU 
> bits or platform are supported!
> Checking for C header file mntent.h... yes
> scons: done reading SConscript files.
> scons: Cleaning targets ...
> scons: done cleaning targets.
> Removing autogenerated directory .sconf_temp
> find . -iname "*.gen.cpp" -delete
> find . -iname "*.gen.h" -delete
> find . -iname "*.pyc" -delete
> find . -iname ".a" -delete
> find . -iname ".o" -delete
> find . -iname ".sconsign.dblite" -delete
> find . -name '*.o' -delete
> rm -rf main/libmain.x11.opt.tools.64.a main/tests/libtests.x11.opt.tools.64.a
> rm -rf config.log .sconsign4.dblite
> rm -rf bin/
> rm -rf enet
> rm -rf freetype
> rm -rf libogg
> rm -rf libpng
> rm -rf libtheora
> rm -rf libvorbis
> rm -rf libvpx
> rm -rf libwebp
> rm -rf openssl
> rm -rf opus
> rm -rf pcre2
> rm -rf squish
> rm -rf zlib
> make[1]: Leaving directory '/<>'
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building godot using existing 
> ./godot_3.2-stable.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: ignoring deletion of file 
> platform/android/java/gradle/wrapper/gradle-wrapper.jar, use 
> --include-removal to override
> dpkg-source: error: cannot represent change to .sconsign5.dblite: binary file 
> contents changed
> dpkg-source: error: add .sconsign5.dblite in debian/source/include-binaries 
> if you want to store the modified binary in the debian tarball
> dpkg-source: error: unrepresentable changes to source
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2020-03-22T02:59:55Z

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/godot_3.2-stable-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: godot
Source-Version: 3.2-stable-2
Done: Juhani Numminen 

We believe that the bug you reported is fixed in the latest version of
godot, 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 

Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>

[Justin Erenkrantz]

James,

Thanks for the bug report.  For reference, the upstream OpenSSL commit
looks to be:

https://github.com/openssl/openssl/commit/d924dbf4ae127c68463bcbece04b6e06abc58928

I strongly suspect that the patch on our side (against 1.3.x) is something
akin to below.  I'm having trouble getting a test environment up with the
latest OpenSSL to reproduce, so if anyone can test in the interim, that'd
be appreciated.  If not, I'll try again as time (and kiddo) permit.

Cheers.  -- justin

Index: buckets/ssl_buckets.c

===

--- buckets/ssl_buckets.c (revision 1875631)

+++ buckets/ssl_buckets.c (working copy)

@@ -807,6 +807,11 @@

 if (ctx->pending_err) {

 status = ctx->pending_err;

 ctx->pending_err = 0;

+} else if (ctx->decrypt.status ==
SSL_R_UNEXPECTED_EOF_WHILE_READING) {

+serf__log(SSL_VERBOSE, __FILE__,

+  "ssl_decrypt: SSL read error: server"

+  " shut down connection!\n");

+status = APR_EOF;

 } else {

 ctx->fatal_err = status = SERF_ERROR_SSL_COMM_FAILED;

 }



On Mon, Mar 23, 2020 at 8:08 PM James McCoy  wrote:

> Looping in upstream:
>
> On Sun, Mar 22, 2020 at 02:57:54PM +0100, Lucas Nussbaum wrote:
> > Version: 1.3.9-8
>
> This is the same version of the serf package that's been in Debian since
> 2019/12/31, so something else seems to have changed.
>
> > [...]
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> >
> > Relevant part (hopefully):
> > > [...]
> > > Trailer-Test: f
> > > 140691743627136:error:14095126:SSL routines:ssl3_read_n:unexpected eof
> while reading:../ssl/record/rec_layer_s3.c:302:
> > > ..F...
> > >
> > > There was 1 failure:
> > > 1) test_ssltunnel_basic_auth_server_has_keepalive_off:
> test/test_context.c:2138: expected <0> but was <120199>
>
> Running a bisect against what's changed in the archive, shows that the
> test started failing when OpenSSL's version changed from 1.1.1d-2 to
> 1.1.1e-1.
>
> Looking at OpenSSL's changelog, it seems this was a change on their end
> that's affecting serf.
>
>  Changes between 1.1.1d and 1.1.1e [17 Mar 2020]
>   *) Properly detect EOF while reading in libssl. Previously if we hit an
> EOF
>  while reading in libssl then we would report an error back to the
>  application (SSL_ERROR_SYSCALL) but errno would be 0. We now add
>  an error to the stack (which means we instead return SSL_ERROR_SSL)
> and
>  therefore give a hint as to what went wrong.
>  [Matt Caswell]
>
> I guess serf needs to adapt to this change in behavior.
>
> Cheers,
> --
> James
> GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB
>

Processed: tagging 954222

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 954222 + pending
Bug #954222 [src:appdirs] src:appdirs: Fails autopkgtest with non-default 
python3 installed
Ignoring request to alter tags of bug #954222 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954915: [libc6] upgrade fail: A copy of the C library was found in an unexpected directory

[Aurelien Jarno]

On 2020-03-25 10:21, Jörg Sommer wrote:
> jnq...@gmail.com hat am Mi 25. Mär, 09:03 (+) geschrieben:
> > Package: libc6
> > Version: 2.30-3
> > 
> > sudo aptitude upgrade just now:
> > 
> > ```
> > Preparing to unpack .../libc6-dev_2.30-3_amd64.deb ...
> > Unpacking libc6-dev:amd64 (2.30-3) over (2.30-2) ...
> > Preparing to unpack .../libc-dev-bin_2.30-3_amd64.deb ...
> > Unpacking libc-dev-bin (2.30-3) over (2.30-2) ...
> > Preparing to unpack .../libc6-dbg_2.30-3_amd64.deb ...
> > Unpacking libc6-dbg:amd64 (2.30-3) over (2.30-2) ...
> > Preparing to unpack .../libc6_2.30-3_amd64.deb ...
> > 
> > A copy of the C library was found in an unexpected directory:
> >   '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
> > It is not safe to upgrade the C library in this situation;
> > please remove that copy of the C library or get it out of
> > '/usr/lib/x86_64-linux-gnu' and try again.
> 
> I'm having the same problem. It's caused by the package *usrmerge*, that
> installed the symlinks:
> 
> ```
> % ls -l /*(@)
> lrwxrwxrwx 1 root root  7 Mär  7  2019 /bin -> usr/bin
> lrwxrwxrwx 1 root root  7 Mär  7  2019 /lib -> usr/lib
> lrwxrwxrwx 1 root root  9 Mär  7  2019 /lib32 -> usr/lib32
> lrwxrwxrwx 1 root root  9 Mär  7  2019 /lib64 -> usr/lib64
> lrwxrwxrwx 1 root root 10 Mär  7  2019 /libx32 -> usr/libx32
> lrwxrwxrwx 1 root root  8 Mär  7  2019 /sbin -> usr/sbin
> ```

It happens that the checks in the libc6.preinst were broken, and that
the fix for #954374 just fixed them. It also means that usrmerge broke
those checks but we didn't notice it until now...

I wonder if the best is to just remove all those checks in libc6.preinst.
After all they haven't been useful all those years, although we also got
a few bugs report about broken systems for which we don't know the cause
and that might have been prevented by working checks.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#954926: Acknowledgement (x264: symbol lookup error)

[Christian Petersen]

Yes. Indeed. I'm an idiot as I thought removing ALL packages sourcing
Christian's repo from the system had be done long time ago.

This one: libx264-155 3:0.155.2901+git7d0ff22-dmo3 was a silient
keeper though.


Thanks for your patience.

Bug can be closed/thrown into the pit.

Processed: Link to upstream issue

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 954632 
> https://github.com/unknown-horizons/unknown-horizons/pull/2910
Bug #954632 [src:unknown-horizons] unknown-horizons: FTBFS: AttributeError: 
module 'platform' has no attribute 'dist'
Set Bug forwarded-to-address to 
'https://github.com/unknown-horizons/unknown-horizons/pull/2910'.
> tags 954632 + upstream fixed-upstream
Bug #954632 [src:unknown-horizons] unknown-horizons: FTBFS: AttributeError: 
module 'platform' has no attribute 'dist'
Added tag(s) upstream and fixed-upstream.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
954632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954926: marked as done (x264: symbol lookup error)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 12:24:05 +0100
with message-id <20200325112405.ga4115...@ramacher.at>
and subject line Re: Bug#954926: x264: symbol lookup error
has caused the Debian Bug report #954926,
regarding x264: symbol lookup error
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.)


-- 
954926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: x264
Version: 2:0.155.2917+git0a84d98-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

x264 (latest package from upstream does not) exites on my testing setup:

(gdb)
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
/usr/bin/x264: symbol lookup error: /usr/bin/x264: undefined symbol:
x264_stack_align
[Inferior 1 (process 137998) exited with code 0177]



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)

Versions of packages x264 depends on:
ii  libavcodec587:4.2.2-1+b1
ii  libavformat58   7:4.2.2-1+b1
ii  libavresample4  7:4.2.2-1+b1
ii  libavutil56 7:4.2.2-1+b1
ii  libc6   2.30-2
ii  libffms2-4  2.23-4
ii  libgpac40.5.2-426-gc5ad4e4+dfsg5-5
ii  libswresample3  7:4.2.2-1+b1
ii  libswscale5 7:4.2.2-1+b1
ii  libx264-155 3:0.155.2901+git7d0ff22-dmo3
ii  zlib1g  1:1.2.11.dfsg-2

x264 recommends no packages.

x264 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On 2020-03-25 12:07:26, Christian Petersen wrote:
> Package: x264
> Version: 2:0.155.2917+git0a84d98-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> x264 (latest package from upstream does not) exites on my testing setup:
> 
> (gdb)
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> /usr/bin/x264: symbol lookup error: /usr/bin/x264: undefined symbol:
> x264_stack_align
> [Inferior 1 (process 137998) exited with code 0177]
> 
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.4.0-4-amd64 (SMP w/2 CPU cores)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> 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)
> 
> Versions of packages x264 depends on:
> ii  libavcodec587:4.2.2-1+b1
> ii  libavformat58   7:4.2.2-1+b1
> ii  libavresample4  7:4.2.2-1+b1
> ii  libavutil56 7:4.2.2-1+b1
> ii  libc6   2.30-2
> ii  libffms2-4  2.23-4
> ii  libgpac40.5.2-426-gc5ad4e4+dfsg5-5
> ii  libswresample3  7:4.2.2-1+b1
> ii  libswscale5 7:4.2.2-1+b1
> ii  libx264-155 3:0.155.2901+git7d0ff22-dmo3

Using packages from dmo is not supported. If you mix packages from
Debian and there, you get to keep the pieces.

Best

> ii  zlib1g  1:1.2.11.dfsg-2
> 
> x264 recommends no packages.
> 
> x264 suggests no packages.
> 
> -- no debconf information
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---

Bug#954916: another breakage due to LaTeX changes?

[Norbert Preining]

On Wed, 25 Mar 2020, Joseph Wright wrote:
> The structure of the .dtx is ... unusual. It's got the \begin{document} in

Yes, this is what I saw, too, but it was working before ;-)

> 'normal', i.e. moving the \begin{document} line, but I'm not sure if that is
> an acceptable fix.

Can you send a patch?

Thanks

Best

Norbert
--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#954926: x264: symbol lookup error

[Christian Petersen]

Package: x264
Version: 2:0.155.2917+git0a84d98-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

x264 (latest package from upstream does not) exites on my testing setup:

(gdb)
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
/usr/bin/x264: symbol lookup error: /usr/bin/x264: undefined symbol:
x264_stack_align
[Inferior 1 (process 137998) exited with code 0177]



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)

Versions of packages x264 depends on:
ii  libavcodec587:4.2.2-1+b1
ii  libavformat58   7:4.2.2-1+b1
ii  libavresample4  7:4.2.2-1+b1
ii  libavutil56 7:4.2.2-1+b1
ii  libc6   2.30-2
ii  libffms2-4  2.23-4
ii  libgpac40.5.2-426-gc5ad4e4+dfsg5-5
ii  libswresample3  7:4.2.2-1+b1
ii  libswscale5 7:4.2.2-1+b1
ii  libx264-155 3:0.155.2901+git7d0ff22-dmo3
ii  zlib1g  1:1.2.11.dfsg-2

x264 recommends no packages.

x264 suggests no packages.

-- no debconf information

Bug#954916: another breakage due to LaTeX changes?

[Norbert Preining]

On Wed, 25 Mar 2020, Joseph Wright wrote:
> Where can we find lgrind.dtx?

It was attached ...

Norbert

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Processed: tagging 954915

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 954915 + confirmed
Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in 
an unexpected directory
Added tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954916: another breakage due to LaTeX changes?

[Joseph Wright]

On 25/03/2020 11:03, Enrico Gregorio wrote:




On 25 Mar 2020, at 11:57 , Joseph Wright  
wrote:

Hi Norbert,

Where can we find lgrind.dtx?


http://mirrors.ctan.org/support/lgrind/lgrind.dtx

Ciao
Enrico



The structure of the .dtx is ... unusual. It's got the \begin{document} 
in the 'input' stage and the \end{document} 'as normal'. The result is 
"%" ends up with the 'wrong' catcode, which is where the issue arises: 
what should be a comment in the .def is not any longer. It can be fixed 
by making the .dtx 'normal', i.e. moving the \begin{document} line, but 
I'm not sure if that is an acceptable fix.


Joseph

Bug#954916: another breakage due to LaTeX changes?

[Enrico Gregorio]

> On 25 Mar 2020, at 11:57 , Joseph Wright  
> wrote:
> 
> Hi Norbert,
> 
> Where can we find lgrind.dtx?

http://mirrors.ctan.org/support/lgrind/lgrind.dtx

Ciao
Enrico

Bug#954916: another breakage due to LaTeX changes?

[Joseph Wright]

On 25/03/2020 10:47, Norbert Preining wrote:

Hi all, in particular LaTeX group,

it seems that some old documents (.dtx) don't translate anymore
correctly. That might be simply a bug in the old code, but maybe some
oversight in the LaTeX code.

The attached lgrind.dtx was used and always properly build up to recent
changes (2020 LaTeX), but now fails with

LaTeX2e <2020-02-02> patch level 5
L3 programming layer <2020-02-25>
(/usr/share/texlive/texmf-dist/tex/latex/base/ltxdoc.cls
Document Class: ltxdoc 2019/09/16 v2.0y Standard LaTeX documentation class
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2019/12/20 v1.4l Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/base/doc.sty
(/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)))
Writing index file lgrind.idx
Writing glossary file lgrind.glo
(./lgrind.dtx
(/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-dvips.def

! LaTeX Error: Missing \begin{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
  ...
   
l.2 %% T

 his is file `l3backend-dvips.def',
?
! Emergency stop.


Since it contains the
l3backend-dvipds.def
that was recently introduced, I assume there is some breakage with
recent LaTeX.

Any comments?

Please keep Cc, thanks!

All the best

Norbert


Hi Norbert,

Where can we find lgrind.dtx?

Joseph

Bug#954916: another breakage due to LaTeX changes?

[Norbert Preining]

Hi all, in particular LaTeX group,

it seems that some old documents (.dtx) don't translate anymore
correctly. That might be simply a bug in the old code, but maybe some
oversight in the LaTeX code.

The attached lgrind.dtx was used and always properly build up to recent
changes (2020 LaTeX), but now fails with
> LaTeX2e <2020-02-02> patch level 5
> L3 programming layer <2020-02-25>
> (/usr/share/texlive/texmf-dist/tex/latex/base/ltxdoc.cls
> Document Class: ltxdoc 2019/09/16 v2.0y Standard LaTeX documentation class
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2019/12/20 v1.4l Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/base/doc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)))
> Writing index file lgrind.idx
> Writing glossary file lgrind.glo 
> (./lgrind.dtx
> (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-dvips.def
> 
> ! LaTeX Error: Missing \begin{document}.
> 
> See the LaTeX manual or LaTeX Companion for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.2 %% T
> his is file `l3backend-dvips.def',
> ? 
> ! Emergency stop.

Since it contains the
l3backend-dvipds.def
that was recently introduced, I assume there is some breakage with
recent LaTeX.

Any comments?

Please keep Cc, thanks!

All the best

Norbert

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
% \iffalse
%
% This is LGrind.DTX. This was written by:
%
% -  Van Jacobson, Lawrence Berkeley Laboratory (based on
%vgrind by Dave Presotto & William Joy of UC Berkeley),
%the original written for \TeX.
% -  Jerry Leichter of Yale University, modifications for \LaTeX.
% -  George V. Reilly of Brown University, renamed to lgrind
% -  Michael Piefel, Humboldt-University Berlin, for \LaTeXe
%and a thousand little changes
%
% \fi
% \iffalse
%% Based on Van Jacobson's ``tgrindmac'', a macro package for TeX.
%% Modified, 1987 by Jerry Leichter. Put '@' in all internal names.
%% Modified, 1991 by George Reilly. Changed name from tgrind to lgrind.
%% Modified, 1995 by Michael Piefel. Made it work with \LaTeXe.
%%  -1999Hundreds of bells and whistles. No changelog here.
%
%<*dtx>
\ProvidesFile{lgrind.dtx}
  [2002/01/28 v3.67 LGrind environment and supporting stuff]
%
%\NeedsTeXFormat{LaTeX2e}[1996/06/01]
%\ProvidesPackage{lgrind}
%  [2002/01/28 v3.67 LGrind environment and supporting stuff]
%<*driver>
\NeedsTeXFormat{LaTeX2e}[1996/06/01]
\documentclass{ltxdoc}
\CodelineIndex
\RecordChanges
\DocInput{lgrind.dtx}
\end{document}
%
% \fi
%
% \newcommand{\LG}{\textsf{LGrind}}
% \newcommand{\NFSS}{\textsf{NFSS}}
% \frenchspacing
% 
% \GetFileInfo{lgrind.dtx}
% \begin{document}
% \title{The \LG{} package\thanks{This file
% has version number \fileversion, last
% revised \filedate.}}
% \author{Various Artists}
% \date{\filedate}
% \maketitle
% 
% \CheckSum{679}
% 
% \begin{abstract}
% The \LG{} package is a pretty printer for source
% code. It evolved from vgrind, supported \TeX{} (tgrind) and
% \LaTeX{} and now finally \LaTeXe, in particular \NFSS.
% \end{abstract}
% 
% \changes{v1.0}{1985/02/10}{Written}
% \changes{v2.0}{1991/09/06}{Upgrade to \LaTeX2.09}
% \changes{v3.0}{1995/09/24}{Upgrade to \LaTeXe}
% 
% \section{Introduction}
% \subsection{What is it?}
% The \LG{} package consists of three files:
% \begin{itemize}
% \item \texttt{lgrind} or \texttt{lgrind.exe} is the executable. It will
% convert an \LaTeX-File with embedded listings or a source code file
% into a lot of macro-calls.
% \item \texttt{lgrind.sty} provides the environments and macros to make
% the produced mess readable.
% \item \texttt{lgrindef} contains the information
% needed to tell keywords from comments, comments from strings \dots
% \end{itemize}
% 
% \subsection{Who is to blame?}
% \LG{} is not the work of a single one. The program is based on
% \textsf{vgrind} by Dave Presotto \& William Joy of UC Berkeley.
% 
% Van Jacobson wrote \textsf{tgrind} for \TeX. Jerry Leichter
% of Yale University modified it for \LaTeX. George V. Reilly of 
% Brown University changed the name to lgrind and added the
% program-text-within-comments and @-within-\LaTeX{} features,
% and finally
% Michael Piefel of the Humboldt-University Berlin converted it to
% work under \LaTeXe, i.\,e. with \NFSS, and improved the documentation.
%
% However, there have been many contributors who supported the development; in
% particular the range of supported languages is mainly due to them.
% Unfortunately I do not know all of them, but my thanks go to everybody.
% A special Thank You to
% Torsten Sch\"utze for his 

Bug#954915: [libc6] upgrade fail: A copy of the C library was found in an unexpected directory

[Jörg Sommer]

jnq...@gmail.com hat am Mi 25. Mär, 09:03 (+) geschrieben:
> Package: libc6
> Version: 2.30-3
> 
> sudo aptitude upgrade just now:
> 
> ```
> Preparing to unpack .../libc6-dev_2.30-3_amd64.deb ...
> Unpacking libc6-dev:amd64 (2.30-3) over (2.30-2) ...
> Preparing to unpack .../libc-dev-bin_2.30-3_amd64.deb ...
> Unpacking libc-dev-bin (2.30-3) over (2.30-2) ...
> Preparing to unpack .../libc6-dbg_2.30-3_amd64.deb ...
> Unpacking libc6-dbg:amd64 (2.30-3) over (2.30-2) ...
> Preparing to unpack .../libc6_2.30-3_amd64.deb ...
> 
> A copy of the C library was found in an unexpected directory:
>   '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
> It is not safe to upgrade the C library in this situation;
> please remove that copy of the C library or get it out of
> '/usr/lib/x86_64-linux-gnu' and try again.

A quick and dirty workaround is:

```
# egrep '/(ld|lib(d|c|m|pthread|rt|dl))-2.*.so' $I/libc6:amd64.list |sed 
's,^,/usr,' |tee -a $I/libc6:amd64.list
/usr/lib/x86_64-linux-gnu/ld-2.30.so
/usr/lib/x86_64-linux-gnu/libc-2.30.so
/usr/lib/x86_64-linux-gnu/libdl-2.30.so
/usr/lib/x86_64-linux-gnu/libm-2.30.so
/usr/lib/x86_64-linux-gnu/libpthread-2.30.so
/usr/lib/x86_64-linux-gnu/librt-2.30.so
# dpkg --unpack $A/libc6_2.30-3_amd64.deb
(Lese Datenbank ... 452795 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../libc6_2.30-3_amd64.deb ...
libc6:i386 (2.30-2) wird de-konfiguriert ...
Entpacken von libc6:amd64 (2.30-3) über (2.30-2) ...

# egrep '/(ld|lib(d|c|m|pthread|rt|dl))-2.*.so' $I/libc6:i386.list |sed 
's,^,/usr,; p; s,/i386-linux-gnu,32,' |tee -a $I/libc6:i386.list
/usr/lib/i386-linux-gnu/ld-2.30.so
/usr/lib32/ld-2.30.so
/usr/lib/i386-linux-gnu/libc-2.30.so
/usr/lib32/libc-2.30.so
/usr/lib/i386-linux-gnu/libdl-2.30.so
/usr/lib32/libdl-2.30.so
/usr/lib/i386-linux-gnu/libm-2.30.so
/usr/lib32/libm-2.30.so
/usr/lib/i386-linux-gnu/libpthread-2.30.so
/usr/lib32/libpthread-2.30.so
/usr/lib/i386-linux-gnu/librt-2.30.so
/usr/lib32/librt-2.30.so
# dpkg --unpack $A/libc6_2.30-3_i386.deb
(Lese Datenbank ... 452801 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../archives/libc6_2.30-3_i386.deb ...
Entpacken von libc6:i386 (2.30-3) über (2.30-2) ...
```

Pay attention: The command for sed for i386 is different from amd64!



-- 
The UNIX Guru's View of Sex:
# unzip ; strip ; touch ; finger ; mount ; fsck ; more ; yes ; umount ; sleep


signature.asc
Description: PGP signature

Bug#954915: [libc6] upgrade fail: A copy of the C library was found in an unexpected directory

[Jörg Sommer]

jnq...@gmail.com hat am Mi 25. Mär, 09:03 (+) geschrieben:
> Package: libc6
> Version: 2.30-3
> 
> sudo aptitude upgrade just now:
> 
> ```
> Preparing to unpack .../libc6-dev_2.30-3_amd64.deb ...
> Unpacking libc6-dev:amd64 (2.30-3) over (2.30-2) ...
> Preparing to unpack .../libc-dev-bin_2.30-3_amd64.deb ...
> Unpacking libc-dev-bin (2.30-3) over (2.30-2) ...
> Preparing to unpack .../libc6-dbg_2.30-3_amd64.deb ...
> Unpacking libc6-dbg:amd64 (2.30-3) over (2.30-2) ...
> Preparing to unpack .../libc6_2.30-3_amd64.deb ...
> 
> A copy of the C library was found in an unexpected directory:
>   '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
> It is not safe to upgrade the C library in this situation;
> please remove that copy of the C library or get it out of
> '/usr/lib/x86_64-linux-gnu' and try again.

I'm having the same problem. It's caused by the package *usrmerge*, that
installed the symlinks:

```
% ls -l /*(@)
lrwxrwxrwx 1 root root  7 Mär  7  2019 /bin -> usr/bin
lrwxrwxrwx 1 root root  7 Mär  7  2019 /lib -> usr/lib
lrwxrwxrwx 1 root root  9 Mär  7  2019 /lib32 -> usr/lib32
lrwxrwxrwx 1 root root  9 Mär  7  2019 /lib64 -> usr/lib64
lrwxrwxrwx 1 root root 10 Mär  7  2019 /libx32 -> usr/libx32
lrwxrwxrwx 1 root root  8 Mär  7  2019 /sbin -> usr/sbin
```

Regards Jörg

-- 
Habe Mut, dich deines eigenen Verstandes zu bedienen! – Immanuel Kant


signature.asc
Description: PGP signature

Bug#954203: Client splash and exit after login in

[Bernhard Übelacker]

Hello Gulfstream,


> Thanks for your reply! My next question is How to connect the xrdp server 
> using remmina client? I don't find where to set the glyph cache.

in the previous mentioned upstream link to the remmina bug
tracker in comment [1] is written that they added such flags,
but I guess the version in buster does not yet contain it.

My best hint would be to check for it in the version
in buster-backports, as a workaround.


> ... And When will the bug be resolve?

This has to be answered by the xrdp maintainers.


Kind regards,
Bernhard

[1] https://gitlab.com/Remmina/Remmina/issues/1770#note_120907885

Bug#954568: marked as done (gcc-10-cross: FTBFS: x86_64-linux-gnu-ld: /lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to `__twalk_r@GLIBC_PRIVATE')

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 10:57:41 +0100
with message-id <82cca473-f6bb-da29-ced8-3b277ad61...@debian.org>
and subject line Re: Bug#954568: gcc-10-cross: FTBFS: x86_64-linux-gnu-ld: 
/lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to 
`__twalk_r@GLIBC_PRIVATE'
has caused the Debian Bug report #954568,
regarding gcc-10-cross: FTBFS: x86_64-linux-gnu-ld: 
/lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to 
`__twalk_r@GLIBC_PRIVATE'
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.)


-- 
954568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-10-cross
Version: 4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[5]: Entering directory '/<>/gcc/build/gotools'
> /<>/gcc/build/./gcc/gccgo -B/<>/gcc/build/./gcc/ 
> -B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem 
> /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/sys-include 
> -isystem /<>/gcc/build/sys-include   -g -O2 -I 
> ../x86_64-linux-gnu/libgo -static-libstdc++ -static-libgcc -Wl,-z,relro -L 
> ../x86_64-linux-gnu/libgo -L ../x86_64-linux-gnu/libgo/.libs -o go 
> ../../src/gotools/../libgo/go/cmd/go/alldocs.go 
> ../../src/gotools/../libgo/go/cmd/go/go11.go 
> ../../src/gotools/../libgo/go/cmd/go/main.go 
> ../x86_64-linux-gnu/libgo/libgotool.a  
> /<>/gcc/build/./gcc/gccgo -B/<>/gcc/build/./gcc/ 
> -B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem 
> /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/sys-include 
> -isystem /<>/gcc/build/sys-include   -g -O2 -I 
> ../x86_64-linux-gnu/libgo -static-libstdc++ -static-libgcc -Wl,-z,relro -L 
> ../x86_64-linux-gnu/libgo -L ../x86_64-linux-gnu/libgo/.libs -o gofmt 
> ../../src/gotools/../libgo/go/cmd/gofmt/doc.go 
> ../../src/gotools/../libgo/go/cmd/gofmt/gofmt.go 
> ../../src/gotools/../libgo/go/cmd/gofmt/internal.go 
> ../../src/gotools/../libgo/go/cmd/gofmt/rewrite.go 
> ../../src/gotools/../libgo/go/cmd/gofmt/simplify.go 
> ../x86_64-linux-gnu/libgo/libgotool.a  
> echo 'package main' > zdefaultcc.go.tmp
> /<>/gcc/build/./gcc/gccgo -B/<>/gcc/build/./gcc/ 
> -B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem 
> /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/sys-include 
> -isystem /<>/gcc/build/sys-include   -g -O2 -I 
> ../x86_64-linux-gnu/libgo -static-libstdc++ -static-libgcc -Wl,-z,relro -L 
> ../x86_64-linux-gnu/libgo -L ../x86_64-linux-gnu/libgo/.libs -o vet 
> ../../src/gotools/../libgo/go/cmd/vet/doc.go 
> ../../src/gotools/../libgo/go/cmd/vet/main.go 
> ../x86_64-linux-gnu/libgo/libgotool.a  
> echo 'func defaultGCCGO(goos, goarch string) string { return 
> "/usr/bin/x86_64-linux-gnu-gccgo-10" }' >> zdefaultcc.go.tmp
> echo 'func defaultCC(goos, goarch string) string { return 
> "x86_64-linux-gnu-gcc-10" }' >> zdefaultcc.go.tmp
> echo 'func defaultCXX(goos, goarch string) string { return 
> "x86_64-linux-gnu-g++-10" }' >> zdefaultcc.go.tmp
> echo 'const defaultPkgConfig = "pkg-config"' >> zdefaultcc.go.tmp
> /bin/bash ../../src/gotools/../move-if-change zdefaultcc.go.tmp zdefaultcc.go
> echo timestamp > s-zdefaultcc 
> /<>/gcc/build/./gcc/gccgo -B/<>/gcc/build/./gcc/ 
> -B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem 
> /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/sys-include 
> -isystem /<>/gcc/build/sys-include   -g -O2 -I 
> ../x86_64-linux-gnu/libgo -static-libstdc++ -static-libgcc -Wl,-z,relro -L 
> ../x86_64-linux-gnu/libgo -L ../x86_64-linux-gnu/libgo/.libs -o buildid 
> ../../src/gotools/../libgo/go/cmd/buildid/buildid.go 
> ../../src/gotools/../libgo/go/cmd/buildid/doc.go 
> ../x86_64-linux-gnu/libgo/libgotool.a  
> /usr/bin/x86_64-linux-gnu-ld: /lib/x86_64-linux-gnu/libpthread.so.0: 
> undefined reference to `__twalk_r@GLIBC_PRIVATE'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/gcc-10-cross_4_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 ---

Bug#954608: godot: Team upload

[Juhani Numminen]

Control: tags -1 +pending

Dear Federico,

I have prepared an upload for godot/3.2-stable-2 as a team upload,
as the package's maintainer is Debian Games Team. The upload should
fix #944168 and #954608. I am looking for a sponsor to upload it.

The code is at https://salsa.debian.org/jnumm-guest/godot3

Please let me know if this is not okay with you.

Regards,
Juhani

Processed: godot: Team upload

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +pending
Bug #954608 [src:godot] godot: FTBFS: dpkg-buildpackage: error: dpkg-source -b 
. subprocess returned exit status 2
Added tag(s) pending.

-- 
954608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954916: lgrind: FTBFS with current texlive

[Andreas Beckmann]

Source: lgrind,texlive-base
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source
Control: found -1 3.67-3.1
Control: found -1 2020.20200313-1

Hi,

lgrind FTBFS with the current texlive in bullseye and sid:

 debian/rules build
dh_testdir
latex lgrind.ins
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./lgrind.ins
LaTeX2e <2020-02-02> patch level 5
L3 programming layer <2020-02-25>
(/usr/share/texlive/texmf-dist/tex/latex/base/docstrip.tex
Utility: `docstrip' 2.5g <2018/05/03>
English documentation<2018/05/03>

**
* This program converts documented macro-files into fast *
* loadable files by stripping off (nearly) all comments! *
**


* No Configuration file found, using default settings. *


(./lgrind.ins

Generating file(s) ./lgrind.sty 

Processing file lgrind.dtx (package) -> lgrind.sty
File lgrind.dtx ended by \endinput.
Lines  processed: 1173
Comments removed: 921
Comments  passed: 8
Codelines passed: 228


Generating file(s) ./doc-lgrind.lg 

Processing file lgrind.dtx (example) -> doc-lgrind.lg
File lgrind.dtx ended by \endinput.
Lines  processed: 1173
Comments removed: 921
Comments  passed: 8
Codelines passed: 228

)
Overall statistics:
Files  processed: 2
Lines  processed: 2346
Comments removed: 1842
Comments  passed: 16
Codelines passed: 456
 ) )
No pages of output.
Transcript written on lgrind.log.
latex lgrind.dtx
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./lgrind.dtx
LaTeX2e <2020-02-02> patch level 5
L3 programming layer <2020-02-25>
(/usr/share/texlive/texmf-dist/tex/latex/base/ltxdoc.cls
Document Class: ltxdoc 2019/09/16 v2.0y Standard LaTeX documentation class
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2019/12/20 v1.4l Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/base/doc.sty
(/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)))
Writing index file lgrind.idx
Writing glossary file lgrind.glo 
(./lgrind.dtx
(/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-dvips.def

! LaTeX Error: Missing \begin{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...  
  
l.2 %% T
his is file `l3backend-dvips.def',
? 
! Emergency stop.
 ...  
  
l.2 %% T
his is file `l3backend-dvips.def',
No pages of output.
Transcript written on lgrind.log.
make: *** [debian/rules:13: build-stamp] Error 1


I'm not sure whether the error is in lgrind or texlive.
Attached are
* a build log from bullseye (the same error occurs in sid)
* pdflatex's lgrind.log from sid


Andreas


lgrind_3.67-3.1.log.gz
Description: application/gzip


lgrind.log.gz
Description: application/gzip

Processed: lgrind: FTBFS with current texlive

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.67-3.1
Bug #954916 [src:lgrind,src:texlive-base] lgrind: FTBFS with current texlive
The source 'texlive-base' and version '3.67-3.1' do not appear to match any 
binary packages
Marked as found in versions lgrind/3.67-3.1 and texlive-base/3.67-3.1.
> found -1 2020.20200313-1
Bug #954916 [src:lgrind,src:texlive-base] lgrind: FTBFS with current texlive
The source 'lgrind' and version '2020.20200313-1' do not appear to match any 
binary packages
Marked as found in versions texlive-base/2020.20200313-1 and 
lgrind/2020.20200313-1.

-- 
954916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 954915 serious
Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in 
an unexpected directory
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
954915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#953069: libgnatcoll-db: FTBFS on mipsel with assembler message: branch out of range

[Aurelien Jarno]

Hi,

On 2020-03-12 13:55, Emilio Pozuelo Monfort wrote:
> Control: severity -1 serious
> 
> On Wed, 4 Mar 2020 01:53:25 +0100 Nicolas Boulenguez  
> wrote:
> > Source: libgnatcoll-db
> > Version: 19.2-2
> > Severity: normal
> > 
> > The relevant lines are:
> > 
> > xref/gnatcoll-xref.adb: In function ‘GNATCOLL.XREF’:
> > xref/gnatcoll-xref.adb:40:1: note: variable tracking size limit exceeded 
> > with ‘-fvar-tracking-assignments’, retrying without
> > Assembler messages:
> > 678119: Error: branch out of range
> 
> This package has old binaries in mipsel, so this failure is RC as it prevents
> the package from migrating to testing.
 
I have just got aware of this bug as it indirectly prevents gcc-8
removal and makes the GCC maintainer angry. In the future don't hesitate
to Cc: the debian-m...@lists.debian.org mailing list so that porters can
be aware of the issue.

My knowledge of ADA is very limited, so I am not sure I fully understood
the problem. However please find below a first workaround using the
-mxgot option to increase the size of the GOT and allow bigger jumps.

--- libgnatcoll-db-19.2/debian/rules2019-12-17 11:41:57.0 +
+++ libgnatcoll-db-19.2/debian/rules2020-03-25 08:40:59.0 +
@@ -26,6 +26,12 @@
 include /usr/share/dpkg/buildflags.mk
 include /usr/share/ada/debian_packaging-$(GNAT_VERSION).mk
 
+# On mipsel gnatcoll-xref.adb generates long jump that do not fit in
+# standard branch instructions. Use the mxgot option to workaround that.
+ifeq ($(DEB_HOST_ARCH),mipsel)
+DEB_CFLAGS_MAINT_APPEND := -mxgot
+endif
+
 # The scenario variables passed to gprbuild and dh_ada_library.
 BUILD := PROD
 GNATCOLL_SQLITE := external

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#954147: marked as done (src:dateparser: Requires a package outside of Main)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 08:45:04 +
with message-id 
and subject line Bug#954147: fixed in dateparser 0.7.2-2
has caused the Debian Bug report #954147,
regarding src:dateparser: Requires a package outside of Main
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.)


-- 
954147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dateparser
Version: 0.7.2-1
Severity: serious
Justification: Policy 2.2.1

This package uses python pip to download and install packages from outside the
Debian archive to run autopkgtests.  Main is required to be self-contained,
including for tests.  See the FTP Master's reject FAQ [1] item Non-Main II.

An excerpt from a recent autpkgtest log is included below to demonstrate the
issue with this package.

Scott K

[1] https://ftp-master.debian.org/REJECT-FAQ.html

autopkgtest [11:23:23]: test command1: pip3 install -U -rrequirements.txt 
-rtests/requirements.txt ; nosetests3 tests
autopkgtest [11:23:23]: test command1: [---
Collecting convertdate==2.1.3 (from -r requirements.txt (line 1))
  Downloading 
https://files.pythonhosted.org/packages/74/83/d0fa07078f4d4ae473a89d7d521aafc66d82641ea0af0ef04a47052e8f17/convertdate-2.1.3-py2.py3-none-any.whl
Collecting jdatetime==3.1.0 (from -r requirements.txt (line 2))
  Downloading 
https://files.pythonhosted.org/packages/c6/9d/1391454b7afdf8d35b85a7658598ad2e363b74b723cdf75431e040f1c010/jdatetime-3.1.0.tar.gz
Collecting python-dateutil==2.7.5 (from -r requirements.txt (line 3))
  Downloading 
https://files.pythonhosted.org/packages/74/68/d87d9b36af36f44254a8d512cbfc48369103a3b9e474be9bdfe536abfc45/python_dateutil-2.7.5-py2.py3-none-any.whl
 (225kB)
Collecting pytz==2018.9 (from -r requirements.txt (line 4))
  Downloading 
https://files.pythonhosted.org/packages/61/28/1d3920e4d1d50b19bc5d24398a7cd85cc7b9a75a490570d5a30c57622d34/pytz-2018.9-py2.py3-none-any.whl
 (510kB)
Collecting regex==2019.01.24 (from -r requirements.txt (line 5))
  Downloading 
https://files.pythonhosted.org/packages/aa/eb/8a56aaf3a0a2a70cf2e017a8fb1ac5b6bad64a143d3096b0c0282b17ead1/regex-2019.01.24.tar.gz
 (647kB)
Collecting tzlocal==1.5.1 (from -r requirements.txt (line 6))
  Downloading 
https://files.pythonhosted.org/packages/cb/89/e3687d3ed99bc882793f82634e9824e62499fdfdc4b1ae39e211c5b05017/tzlocal-1.5.1.tar.gz
Collecting umalqurra==0.2 (from -r requirements.txt (line 7))
  Downloading 
https://files.pythonhosted.org/packages/59/d7/d57cfbf2ef0fd5f79c94bb4cc1fdb9af49eba592556e4e6891e2d5522fba/umalqurra-0.2.tar.gz
Collecting mock (from -r tests/requirements.txt (line 1))
  Downloading 
https://files.pythonhosted.org/packages/30/6a/9bde648117ec7087c89a45de0a8b25aba21d54d3defd08cb24eacded875f/mock-4.0.1-py3-none-any.whl
Requirement already up-to-date: nose in /usr/lib/python3/dist-packages (from -r 
tests/requirements.txt (line 2)) (1.3.7)
Collecting parameterized (from -r tests/requirements.txt (line 3))
  Downloading 
https://files.pythonhosted.org/packages/a3/bf/6ef8239028beae8298e0806b4f79c2466b1b16ca5b85dc13d631c5ea92c4/parameterized-0.7.1-py2.py3-none-any.whl
Requirement already up-to-date: six in /usr/lib/python3/dist-packages (from -r 
tests/requirements.txt (line 4)) (1.14.0)
Collecting coverage (from -r tests/requirements.txt (line 5))
  Downloading 
https://files.pythonhosted.org/packages/9a/08/7fa92679a903cac0e01a7fee2cadd92089d96a3002c34e8f2295b80d6b68/coverage-5.0.3-cp37-cp37m-manylinux1_x86_64.whl
 (227kB)
Requirement already satisfied, skipping upgrade: ephem<3.8,>=3.7.5.3 in 
/usr/lib/python3/dist-packages (from convertdate==2.1.3->-r requirements.txt 
(line 1)) (3.7.7.0)
Building wheels for collected packages: jdatetime, regex, tzlocal, umalqurra
  Running setup.py bdist_wheel for jdatetime: started
  Running setup.py bdist_wheel for jdatetime: finished with status 'done'
  Stored in directory: 
/home/debci/.cache/pip/wheels/94/3f/63/156126007a5089d65f62ee4e7576ec70200a037b094708322e
  Running setup.py bdist_wheel for regex: started
  Running setup.py bdist_wheel for regex: finished with status 'done'
  Stored in directory: 
/home/debci/.cache/pip/wheels/ff/8d/55/2ccfa47df2bc65ea83c605075f690c6338a2da89f82c171133
  Running setup.py bdist_wheel for tzlocal: started
  Running setup.py bdist_wheel for tzlocal: finished with status 'done'
  Stored in directory: 
/home/debci/.cache/pip/wheels/15/ae/df/a67bf1ed84e9bf230187d36d8dcfd30072bea0236cb059ed91
  Running setup.py bdist_wheel for umalqurra: started
  Running setup.py bdist_wheel for 

Processed: tagging 947568

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 947568 + ftbfs
Bug #947568 [src:mixxx] FTBFS with scons 3.1.2-1
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
947568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954912: Please switch to gupnp/gssdp 1.2

[Laurent Bigonville]

Source: librm
Version: 2.1.2-2
Severity: serious
Tags: patch

Hello,

Could you please switch the build-dependencies to gupnp/gssdp 1.2
instead of 1.0?

We are currently trying to get rid of the version 1.0 librm has
reintroduced a reverse-dependencies against that old version.

Kind regards
Laurent Bigonville

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
diff -Nru librm-2.1.2/debian/control librm-2.1.2/debian/control
--- librm-2.1.2/debian/control  2020-02-04 22:47:40.0 +0100
+++ librm-2.1.2/debian/control  2020-03-25 08:54:31.0 +0100
@@ -13,8 +13,8 @@
  libspandsp-dev,
  libjson-glib-dev,
  libsndfile1-dev,
- libgupnp-1.0-dev,
- libgssdp-1.0-dev,
+ libgupnp-1.2-dev,
+ libgssdp-1.2-dev,
  libcapi20-dev,
  libgstreamer1.0-dev,
  libgstreamer-plugins-base1.0-dev,

Bug#952278: marked as done (kwindowsystem: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 07:49:13 +
with message-id 
and subject line Bug#948827: fixed in kwindowsystem 5.62.0-3
has caused the Debian Bug report #948827,
regarding kwindowsystem: FTBFS: dh_auto_configure: error: cd 
obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON 
-DBUILD_QCH=ON -DBUILD_TESTING=OFF .. returned exit code 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.)


-- 
948827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kwindowsystem
Version: 5.62.0-2
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):
> make[3]: Entering directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> Building C object CMakeFiles/cmTC_b7620.dir/CheckFunctionExists.c.o
> /usr/bin/cc -D_GNU_SOURCE -D_LARGEFILE64_SOURCE  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=iso9899:1990 
> -fno-common -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security 
> -Wno-long-long -Wpointer-arith -Wundef -Wmissing-format-attribute 
> -Wwrite-strings -Werror=implicit-function-declaration 
> -DCHECK_FUNCTION_EXISTS=shmat   -o 
> CMakeFiles/cmTC_b7620.dir/CheckFunctionExists.c.o   -c 
> /usr/share/cmake-3.16/Modules/CheckFunctionExists.c
> Linking C executable cmTC_b7620
> /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_b7620.dir/link.txt 
> --verbose=1
> /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -std=iso9899:1990 -fno-common -Wall -Wextra -Wcast-align 
> -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef 
> -Wmissing-format-attribute -Wwrite-strings 
> -Werror=implicit-function-declaration -DCHECK_FUNCTION_EXISTS=shmat  
> -Wl,--enable-new-dtags -Wl,-z,relro -Wl,--as-needed  
> CMakeFiles/cmTC_b7620.dir/CheckFunctionExists.c.o  -o cmTC_b7620 
> make[3]: Leaving directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> make[2]: Leaving directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> 
> 
> 
> dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake 
> -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON 
> -DBUILD_QCH=ON -DBUILD_TESTING=OFF .. returned exit code 1
> make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/kwindowsystem_5.62.0-2_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: kwindowsystem
Source-Version: 5.62.0-3
Done: Pino Toscano 

We believe that the bug you reported is fixed in the latest version of
kwindowsystem, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 948...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated kwindowsystem package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive

Bug#948827: marked as done (kwindowsystem FTBFS: The XFixes library could not be found.)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 07:49:13 +
with message-id 
and subject line Bug#948827: fixed in kwindowsystem 5.62.0-3
has caused the Debian Bug report #948827,
regarding kwindowsystem FTBFS: The XFixes library could not be found.
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.)


-- 
948827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kwindowsystem
Version: 5.62.0-2
Severity: serious
Tags: ftbfs

kwindowsystem fails to build in unstable. The relevant message seems to
be:

| CMake Error at src/CMakeLists.txt:40 (message):
|   The XFixes library could not be found.  Please install the development
|   package for it.
| 
| 
| -- Configuring incomplete, errors occurred!

Reproduced by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/kwindowsystem_5.62.0-2.rbuild.log.gz
Also seen on crossqa since at least three weeks, but less than seven
weeks:
http://crossqa.debian.net/build/kwindowsystem_5.62.0-2_armhf_20191221224841.log

It seems that for some reason libxfixes-dev is no longer part of the
installation set of the Build-Depends.

Helmut
--- End Message ---
--- Begin Message ---
Source: kwindowsystem
Source-Version: 5.62.0-3
Done: Pino Toscano 

We believe that the bug you reported is fixed in the latest version of
kwindowsystem, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 948...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated kwindowsystem 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, 25 Mar 2020 08:27:34 +0100
Source: kwindowsystem
Architecture: source
Version: 5.62.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Closes: 948827
Changes:
 kwindowsystem (5.62.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Explicitly add the libxcb-xfixes0-dev, and libxfixes-dev build
 dependencies, no more implicitly pulled by other X development packages.
 (Closes: #948827)
   * Bump the debhelper compatibility to 12:
 - switch the debhelper build dependency to debhelper-compat 12
 - remove debian/compat
   * Drop the unused/disabled 'acc' autopkgtest.
   * Bump Standards-Version to 4.5.0, no changes required.
Checksums-Sha1:
 0fbf8d970e6f29b828e17275a8f7eeefdc326c13 2909 kwindowsystem_5.62.0-3.dsc
 a10d61e93ffedf008770d6915c4cad2a36974e4f 13616 
kwindowsystem_5.62.0-3.debian.tar.xz
 3be07f686014b9f8055a54c6032e0e04c587f015 12729 
kwindowsystem_5.62.0-3_source.buildinfo
Checksums-Sha256:
 26d2e42f9c373ef4e25fc2cc246cc1ce23f8842b4ccbfef43ed7259569df120f 2909 
kwindowsystem_5.62.0-3.dsc
 a7976333e86bbb980d3d5554a4c72ecf0f3cea2e50a22d3a8c8a32bbd90bf4fa 13616 
kwindowsystem_5.62.0-3.debian.tar.xz
 a5920240ac2c106e3b586680feb3d558d507dafd7b780857cee104f4d746565f 12729 
kwindowsystem_5.62.0-3_source.buildinfo
Files:
 768fec5eaf919579d570bc884d415c03 2909 libs optional kwindowsystem_5.62.0-3.dsc
 e14eb1f7523aaad894a69cae00516f06 13616 libs optional 
kwindowsystem_5.62.0-3.debian.tar.xz
 38d1b826e49fddb25eb4540827b15155 12729 libs optional 
kwindowsystem_5.62.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAl57CAQACgkQLRkciEOx
P03jSw/+Li0rMv0P0oHS+qeNwubSDSaquniBvnE58BFVTYuffJGNGU6JLUYds0En
lk98VCwf/ZyGe0720tv2s9WisCUiad+sUk47SlxEn1CfWCcIqTRDh2rlMm0yo3gs
RhokWUT1AheqUhLKXAJDuqRwPr/fUku65YwE7IRLdUwWRa7Kxgw2LYvL0GrjZhq8
JkE9cHHBBfDyrw6uLAlDN5mt8/peAQ4K4REaxNku5FOzeA8DWg4hpYDnZjAE+S16
IYbW4sGLMFUlH521cCyHsUgPDizbP/7Vqom+2fO21cqGXhNNZJ590xqz7wjb3xxy
krdcn0z3WxWRbGylQoUXqXJdMLwIkJsIb1qthd0PCfeik9NQVbn31BNp2uthhwNf
zzj5bI2vOlerD7uz1Ksb/B1u5x4hI5hq5cNfjTqxRWkCRN1tBBgqI0wUfvw459Pq
pxxpG16fg9iZ2npdkl+m+QZ6tvCDuu4Ygbyu9uJ7vNNG0au07xOYLlCXEt47V0ZH
sAtcaj301w0AG3HHFgsLXX+x/quJLi7z4Vc9OOCcYAcJgQXXpSAxgsQhy00q91Ls
4Y0wJHLYpx9mFkFxIZyN9yl5tLjC39Fr9GF4PoNSkskw07OgyMmFPUzR/8nbTozc
91c5ywU6jhtwBdRe3IaGkoXBOuvxJsLnRtA1K5OuG7iSFQXgqkk=
=gLtA
-END PGP SIGNATURE End Message ---

Processed: tagging 952240

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 952240 + fixed-in-experimental
Bug #952240 {Done: Christoph Biedl } 
[src:clevis] clevis: FTBFS: dh_install: error: missing files, aborting
Added tag(s) fixed-in-experimental.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
952240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 948827

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 948827 + pending
Bug #948827 [src:kwindowsystem] kwindowsystem FTBFS: The XFixes library could 
not be found.
Bug #952278 [src:kwindowsystem] kwindowsystem: FTBFS: dh_auto_configure: error: 
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON 
-DBUILD_QCH=ON -DBUILD_TESTING=OFF .. returned exit code 1
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
948827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948827
952278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forcibly merging 948827 952278

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 948827 952278
Bug #948827 [src:kwindowsystem] kwindowsystem FTBFS: The XFixes library could 
not be found.
Bug #948827 [src:kwindowsystem] kwindowsystem FTBFS: The XFixes library could 
not be found.
Added tag(s) bullseye and sid.
Bug #952278 [src:kwindowsystem] kwindowsystem: FTBFS: dh_auto_configure: error: 
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON 
-DBUILD_QCH=ON -DBUILD_TESTING=OFF .. returned exit code 1
Merged 948827 952278
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
948827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948827
952278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954203: Re: Bug#954203: Client splash and exit after login in

[wglxy]

Thanks for your reply! My next question is How to connect the xrdp server using 
remmina client? I don't find where to set the glyph cache. And When will the 
bug be resolve?


Thank again!


Best regards,
Gulfstream



> -原始邮件-
> 发件人: "Bernhard Übelacker" 
> 发送时间: 2020-03-21 19:07:38 (星期六)
> 收件人: 954...@bugs.debian.org, gulfstream 
> 抄送: 
> 主题: Re: Bug#954203: Client splash and exit after login in
> 
> Hello,
> this seems to be caused by xrdp using glyph cache even
> when the client does not advertise it.
> Additionally freerdp does now stricter checks.
> 
> Upstream bugs are here [1].
> 
> A workaround could be to use xfreerdp like this:
> 
> xfreerdp +glyph-cache /relax-order-checks /v:hostname
> 
> Kind regards,
> Bernhard
> 
> 
> [1]
> https://github.com/neutrinolabs/xrdp/issues/1266
> 
> https://gitlab.com/Remmina/Remmina/issues/1770
> 
> https://github.com/FreeRDP/FreeRDP/issues/5072
> https://github.com/FreeRDP/FreeRDP/issues/5207

Processed: tags 954619 + fixed-upstream

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 954619 + fixed-upstream
Bug #954619 [src:python-ase] python-ase: FTBFS: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.7 3.8" returned exit code 13
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954905: Can not using optirun to access second GPU and run opengl program

[gulfstream]

Package: bumblebee
Version: 3.2.1-22
Severity: grave


My laptop has two GPU, the first is intel GPU, the second is NVIDIA Quadro 
P2000 Mobile. 

After I install bumblebee, the second GPU can be shut down.

$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e94]
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107GLM [Quadro 
P2000 Mobile] [10de:1cba] (rev ff)

When I want to run opengl program with the second GPU, I run the program using 
optirun, for example: 

$optirun glxgears 

But the opengl program can not be run, and error message is got:

$ optirun glxgears 
[  871.970860] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA: 
Failed to initialize the NVIDIA kernel module. Please see the

[  871.970883] [ERROR]Aborting because fallback start is disabled.


And the second GPU is turned on. If I use lspci command, the message is got as 
below.

$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e94]
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107GLM [Quadro 
P2000 Mobile] [10de:1cba] (rev a1)

Then, I run nvidia-smi, and get the messages:

$ nvidia-smi
Wed Mar 25 14:07:57 2020   
+-+
| NVIDIA-SMI 440.64   Driver Version: 440.64   CUDA Version: N/A  |
|---+--+--+
| GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. |
|===+==+==|
|   0  Quadro P2000 wi...  Off  | :01:00.0 Off |  N/A |
| N/A   46CP0N/A /  N/A |  0MiB /  4040MiB |  2%  Default |
+---+--+--+
   
+-+
| Processes:   GPU Memory |
|  GPU   PID   Type   Process name Usage  |
|=|
|  No running processes found |
+-+


The bumblebee can not manage the second GPU for long time. Would you please 
resolve the problem? Thank you very much!



Best regards,
Gulfstream





-- Package-specific info:
OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root 25 Mar 25 00:03 /etc/alternatives/glx -> 
/usr/lib/nvidia/bumblebee
lrwxrwxrwx 1 root root 51 Mar 25 00:03 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root 48 Mar 25 00:03 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root 50 Mar 25 00:03 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root 54 Mar 25 00:03 
/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 40 Mar 25 00:03 
/etc/alternatives/glx--libGLX_indirect.so.0-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/libGLX_mesa.so.0
lrwxrwxrwx 1 root root 42 Mar 25 00:03 
/etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
lrwxrwxrwx 1 root root 42 Mar 25 00:03 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root 32 Mar 25 00:03 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root 23 Mar 25 00:03 /etc/alternatives/nvidia -> 
/usr/lib/nvidia/current
lrwxrwxrwx 1 root root 57 Mar 25 00:03 
/etc/alternatives/nvidia--libGLX_nvidia.so.0-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/current/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root 59 Mar 25 00:03 
/etc/alternatives/nvidia--libGLX_nvidia.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root 46 Mar 25 00:03 
/etc/alternatives/nvidia--libglxserver_nvidia.so -> 
/usr/lib/nvidia/current/libglxserver_nvidia.so
lrwxrwxrwx 1 root root 58 Mar 25 00:03 
/etc/alternatives/nvidia--libnvidia-ml.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-ml.so.1
lrwxrwxrwx 1 root root 70 Mar 25 00:03 
/etc/alternatives/nvidia--libnvidia-ptxjitcompiler.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-ptxjitcompiler.so.1
lrwxrwxrwx 1 root root 61 Mar 25 00:03 
/etc/alternatives/nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu