Bug#952695: marked as done (r-cran-xml2: autopkgtest failure against libxml2 2.9.10)

[Debian Bug Tracking System]

Your message dated Wed, 04 Mar 2020 07:34:49 +
with message-id 
and subject line Bug#952695: fixed in r-cran-xml2 1.2.2-3
has caused the Debian Bug report #952695,
regarding r-cran-xml2: autopkgtest failure against libxml2 2.9.10
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.)


-- 
952695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-xml2
Version: 1.2.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer,

With a recent upload of libxml2 the autopkgtest of r-cran-xml2 fails
in testing when that autopkgtest is run with the binary packages of
libxml2 from unstable. It passes when run with only packages from
testing.

I believe this to be a proper behavioural change of libxml2, though I
haven't tracked it down to the changing commit.


autopkgtest [18:10:13]: test run-unit-test: [---

R version 3.6.2 (2019-12-12) -- "Dark and Stormy Night"
Copyright (C) 2019 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> library(testthat)
> library(xml2)
>
> test_check("xml2")
This is libxml2 version 2.9.4
-- 1. Failure: url_relative (@test-url.R#22)  --
url_relative("http://hadley.nz/a/c;, "http://hadley.nz/;) not equal to "../a/c".
1/1 mismatches
x[1]: "a/c"
y[1]: "../a/c"

== testthat results  ===
[ OK: 392 | SKIPPED: 3 | WARNINGS: 0 | FAILED: 1 ]
1. Failure: url_relative (@test-url.R#22)

Error: testthat unit tests failed
Execution halted
autopkgtest [18:10:16]: test run-unit-test: ---]


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: r-cran-xml2
Source-Version: 1.2.2-3
Done: michael.cru...@gmail.com (Michael R. Crusoe)

We believe that the bug you reported is fixed in the latest version of
r-cran-xml2, 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.
Michael R. Crusoe  (supplier of updated r-cran-xml2 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 03 Mar 2020 15:58:15 +0100
Source: r-cran-xml2
Architecture: source
Version: 1.2.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Michael R. Crusoe 
Closes: 952695
Changes:
 r-cran-xml2 (1.2.2-3) unstable; urgency=medium
 .
   * Team upload.
   * debian/patches/libxml2_version.patch: Support libxml2 2.9.10 with a patch
 from upstream (Closes: #952695)
Checksums-Sha1:
 a26ac3b80c55ae52524fa7ba66302138a7d37f0c 2081 r-cran-xml2_1.2.2-3.dsc
 e47b1047abeebf7d80ebfe3d13b56ebb2d9841a5 10024 
r-cran-xml2_1.2.2-3.debian.tar.xz
 9dc188bf93a94181a3cc65313dac289b1bba8914 9048 
r-cran-xml2_1.2.2-3_amd64.buildinfo
Checksums-Sha256:
 ac8baa94b926f7f5f3df96bfac9ec6dd2f1b72aaefcefd490ba40a06a5ab9773 2081 
r-cran-xml2_1.2.2-3.dsc
 7a929e3df1806ab427c0d8de55ebbd6eea5ec8d1c6d350d228bc1764b6558d17 10024 
r-cran-xml2_1.2.2-3.debian.tar.xz
 ca3880d532bdb06271be5665200f7007b6122b912305bfac83f33d03114e0cfe 9048 
r-cran-xml2_1.2.2-3_amd64.buildinfo
Files:
 5d10c3918ba821808900fb1b631788bd 2081 gnu-r optional r-cran-xml2_1.2.2-3.dsc
 

Bug#952695: Request for sponsorship or upload rights Re: r-cran-xml2: autopkgtest failure against libxml2 2.9.10

[Dylan Aïssi]

Hi Michael,

On Tue, 3 Mar 2020 16:22:47 +0100 "Michael R. Crusoe"
 wrote:
> I've commited a fix for this bug.
>
>
> If a DD could sponsor that upload or grant me upload rights, I would
> appreciate it.
>

Thanks for this! Just uploaded!

I got an error when I tried to grant you upload rights for this
package, but probably only from my side. I will try to fix it before
the next time.

Best,
Dylan

Bug#953079: fontforge: FTBFS: builds with Python 2.7 by default if it is present and build then fails

[Julian Gilbey]

Package: fontforge
Version: 1:20190801~dfsg-2
Severity: serious
Tags: patch

The configure script prefers Python 2.7 over Python 3.x by default.
This then leads to a build failure as the shlib symbols in
debian/libfontforge3.symbols do not match the symbols in the compiled
libfontforge3.

The easy solution is to change the line in debian/rules which reads

 --enable-python-scripting \

to read

 --enable-python-scripting=3 \

(This is tested and it appears to work.)

Best wishes,

   Julian

Bug#936055: marked as done ([regression] GDB can't printf convenience vars that hold pointers to strings)

[Debian Bug Tracking System]

Your message dated Wed, 04 Mar 2020 05:50:32 +
with message-id 
and subject line Bug#936055: fixed in gdb 9.1-2
has caused the Debian Bug report #936055,
regarding [regression] GDB can't printf convenience vars that hold pointers to 
strings
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.)


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

Package: src:libapp-stacktrace-perl
Version: 0.09-3
Severity: important
Tags: upstream
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=121262

I see you already forwarded this upstream.  Filing the issue, because I also see 
that in Ubuntu at

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/liba/libapp-stacktrace-perl/20190828_222752_2da85@/log.gz

Is there a way to exit with a status for unreliable tests, that gets ignored by 
the autopkg tests?
--- End Message ---
--- Begin Message ---
Source: gdb
Source-Version: 9.1-2
Done: Sergio Durigan Junior 

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

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

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

Debian distribution maintenance software
pp.
Sergio Durigan Junior  (supplier of updated gdb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 03 Mar 2020 23:49:25 -0500
Source: gdb
Architecture: source
Version: 9.1-2
Distribution: unstable
Urgency: medium
Maintainer: Héctor Orón Martínez 
Changed-By: Sergio Durigan Junior 
Closes: 936055
Changes:
 gdb (9.1-2) unstable; urgency=medium
 .
   [ Christian Biesinger ]
   * Load gdbinit files from /etc/gdb/gdbinit.d/*. Files need to have a
 .gdb/.py extension.
   * Fix W-compiler-flags-hidden.
 Set V=1 when building so the full compile commandline is shown.
 Fixes W-compiler-flags-hidden.html from
 https://qa.debian.org/bls/packages/g/gdb.html
 .
   [ Sergio Durigan Junior ]
   * Enable libxxhash during build.
   * Create directory /etc/gdb/gdbinit.d.
 With the new "--with-system-gdbinit-dir" option, we also need to make
 sure the new directory exists.
   * Backport patch to fix printf convenience var regression.
 This was a regression upstream that caused failures on
 libapp-stacktrace-perl. (Closes: #936055)
   * Adjust python-config.patch to use the new "--embed" from Python 3.8's 
config.
 This adjustment is needed because python3.8-config implements a new
 '--embed' option, which should be used by applications building an
 embedded Python interpreter.  For more info, see
 .
   * Enable libmpfr during build.
Checksums-Sha1:
 0ed514bf3d13000ead1fa61d1742f8f11c48b3a6 2850 gdb_9.1-2.dsc
 0bf3688b4971cda5533cdbca005a44c0b49072ed 50988 gdb_9.1-2.debian.tar.xz
 886459e2e400d4b254f19e49c7b19c8e006c0572 10735 gdb_9.1-2_amd64.buildinfo
Checksums-Sha256:
 8512c8f0cda70e8c7dbc887eec5f029fae2d6aed99165334ce1cef2f8efdd79f 2850 
gdb_9.1-2.dsc
 47a3305eba729f795a0bc23cfec6f8d5a7677b89968fd42e98daae51fe80aa0a 50988 
gdb_9.1-2.debian.tar.xz
 e7d35b21d6893c3f5640f549c6153c480fd3a46bda2f9b720f6d3724ecec9361 10735 
gdb_9.1-2_amd64.buildinfo
Files:
 1009f8c9300be9532d6da68bc444df29 2850 devel optional gdb_9.1-2.dsc
 8f01c6427754cad876b1b333abea2d85 50988 devel optional gdb_9.1-2.debian.tar.xz
 b66d8d453011f3d77dcc5244e4d88b17 10735 devel optional gdb_9.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEI3pUsQKHKL8A7zH00Ot2KGX8XjYFAl5fOb8UHHNlcmdpb2Rq
QGRlYmlhbi5vcmcACgkQ0Ot2KGX8XjZQmg//efMs5VXgEYesuAhfPJ+39ZVBS2SQ
9flhWa4dB4mRn8xOQc8V0oufgY9+iJkI8ii7aH4UNZAR+Ijlq6bbQLayISs5rR7O
wq0loUuWHrmQUmejnizqX5sVnBPgtLo0mjljIuOClshx/pjFE/JiMOgcagvCWjY0
eIZi+XWl+T+puSBN9U+iS/rkrYNl6P+2PDesjVrEy4mVchTw/FZ/WZsutoltqgIR
A2JModLO9MYYEy8v7dM2zJpeID/yXjAxhN5sMeaZ/4JPXLToTFA9HCKJm192b9Vf
9FPbhwolba0Tc7MfT0hdD9WxGLWuD8wvcgIuaTd3LXOWMgoPslASD5JSEYiXXRup
2CBiZTCKA+doThI8i3JT0A+wC5KDqcpVbjFLqayZ+f5SGK1nbYNw2Atro1W733ts
d6o3NOubC8BS8gcDNP7SfUIB855DDn5XhwUsqr5Cte+6D+4EljFLSG4D3qW84bqa

Bug#947297: marked as done (ipykernel-py2: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 04 Mar 2020 05:35:12 +
with message-id 
and subject line Bug#952952: Removed package(s) from unstable
has caused the Debian Bug report #947297,
regarding ipykernel-py2: 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.)


-- 
947297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ipykernel-py2
Version: 4.10.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, in details:

(source:ipykernel-py2)Build-Depends->python
(source:ipykernel-py2)Build-Depends->python-faulthandler
(source:ipykernel-py2)Build-Depends->python-ipython
(source:ipykernel-py2)Build-Depends->python-jupyter-client
(source:ipykernel-py2)Build-Depends->python-matplotlib
(source:ipykernel-py2)Build-Depends->python-mock
(source:ipykernel-py2)Build-Depends->python-nose
(source:ipykernel-py2)Build-Depends->python-pickleshare
(source:ipykernel-py2)Build-Depends->python-setuptools
(source:ipykernel-py2)Build-Depends->python-tornado
(source:ipykernel-py2)Build-Depends->python-traitlets
(source:ipykernel-py2)Testsuite-Triggers->python-mock
(source:ipykernel-py2)Testsuite-Triggers->python-nose
(source:ipykernel-py2)Testsuite-Triggers->python-pytest
(binary:python-ipykernel)Depends->python-ipython
(binary:python-ipykernel)Depends->python-jupyter-client
(binary:python-ipykernel)Depends->python-tornado
(binary:python-ipykernel)Depends->python-traitlets
(binary:python-ipykernel)Depends->python2:any
(binary:python-ipykernel)Depends->python2:any

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 there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 4.10.1-4+rm

Dear submitter,

as the package ipykernel-py2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/952952

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#952071: marked as done (ruby-extendmatrix: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError:)

[Debian Bug Tracking System]

Your message dated Wed, 04 Mar 2020 05:36:07 +
with message-id 
and subject line Bug#953041: Removed package(s) from unstable
has caused the Debian Bug report #952071,
regarding ruby-extendmatrix: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError:
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.)


-- 
952071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-extendmatrix
Version: 0.3.1-3
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):
>   NoMethodError:
> undefined method `init_rows' for Matrix[[3, 1, 1], [1, 3, 1], [1, 1, 
> 3]]:Matrix
>   # ./lib/extendmatrix.rb:327:in `initialize_copy'
>   # ./lib/extendmatrix.rb:1096:in `initialize_clone'
>   # ./lib/extendmatrix.rb:1096:in `clone'
>   # ./lib/extendmatrix.rb:1096:in `cJacobi'
>   # ./lib/extendmatrix.rb:1116:in `cJacobiA'
>   # ./spec/extendmatrix_spec.rb:414:in `block (2 levels) in  (required)>'
> 
> Deprecation Warnings:
> 
> Using `should` from rspec-expectations' old `:should` syntax without 
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or 
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = 
> :should }` instead. Called from 
> /<>/spec/extendmatrix_spec.rb:16:in `block (2 levels) in  (required)>'.
> 
> 
> 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.01379 seconds (files took 0.1885 seconds to load)
> 64 examples, 14 failures
> 
> Failed examples:
> 
> rspec ./spec/extendmatrix_spec.rb:255 # Matrix class extension: equal_in_delta
> rspec ./spec/extendmatrix_spec.rb:285 # Matrix class extension: eigen
> rspec ./spec/extendmatrix_spec.rb:309 # Matrix class extension: LU 
> rspec ./spec/extendmatrix_spec.rb:319 # Matrix class extension: L 
> rspec ./spec/extendmatrix_spec.rb:328 # Matrix class extension: U 
> rspec ./spec/extendmatrix_spec.rb:337 # Matrix class extension: houseQR 
> rspec ./spec/extendmatrix_spec.rb:347 # Matrix class extension: houseR 
> rspec ./spec/extendmatrix_spec.rb:356 # Matrix class extension: 
> bidiagonalization
> rspec ./spec/extendmatrix_spec.rb:366 # Matrix class extension: gram_schmidt
> rspec ./spec/extendmatrix_spec.rb:377 # Matrix class extension: givens 
> rspec ./spec/extendmatrix_spec.rb:382 # Matrix class extension: hessenbergQR 
> rspec ./spec/extendmatrix_spec.rb:399 # Matrix class extension: 
> hessenberg_form 
> rspec ./spec/extendmatrix_spec.rb:405 # Matrix class extension: realSchur
> rspec ./spec/extendmatrix_spec.rb:411 # Matrix class extension: Classic 
> Jacobi algorithm
> 
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
> --pattern ./spec/\*_spec.rb failed
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/ruby-extendmatrix_0.3.1-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 0.3.1-3+rm

Dear submitter,

as the package ruby-extendmatrix has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/953041

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing

Processed: Re: Bug#952742: mumble: start locks sound for all application (even the client itself)

[Debian Bug Tracking System]

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

> severity 952742 important
Bug #952742 [mumble] mumble: start locks sound for all application (even the 
client itself)
Severity set to 'important' from 'grave'
> tags 952742 + moreinfo unreproducible
Bug #952742 [mumble] mumble: start locks sound for all application (even the 
client itself)
Added tag(s) moreinfo and unreproducible.
> thanks
Stopping processing here.

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

Bug#952742: mumble: start locks sound for all application (even the client itself)

[Chris Knadle]

severity 952742 important
tags 952742 + moreinfo unreproducible
thanks

lemmel:
> Package: mumble
> Version: 1.3.0+dfsg-1+b1
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> fresh dist-upgrade (this day 02/28/20) brought up a mumble that lock all sound
> on the host, the mumble client itself producing no sound.
> 
> I did all kind of setup with the mumble client (OSS, ALSA, etc), but it did
> nothing.

I upgraded a VM running native Sid + Buster and did a full upgrade, and found
audio with Mumble 1.3.0+dfsg-1+b1 via pulseaudio worked fine.  I tried using
ALSA with Mumble, and was not able to get that to work with the "[default]
Playback/recording through the PulseAudio sound server" setting, and haven't
tried further settings (yet).  I tried OSS with Mumble and was not able to get
that to work, but that didn't surprise me.

Concerning Debian Sid/Unstable, my understanding is that it is not a complete
distribution, and so Unstable is meant to be run as Unstable + Stable, i.e. Sid
+ Buster.  Looking at the distributions you're currently using I see it's
Unstable + Testing, i.e. Sid + Bullseye.  I'm not sure if that may explain this
bug or not; I may try to take a VM snapshot and upgrade to Sid + Bullseye and
see if I can get the audio in Mumble to crap out.

But for now I'm marking the severity of this bug as "important" rather than
"grave" because as best I can tell it's broken on your system but not others.
[If other users hit this bug when running Sid + Buster, please report that to
this bug.]

It's also possible this might be AppArmor related, because Mumble doesn't ship
an AppArmor profile at the moment, and I see you've got AppArmor enabled.

[...]

> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr 
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled

The best place I know to get more helpful advice in tracking down the audio
difficulty is the #mumble IRC channel on irc.freenode.net.  There are users in
the IRC channel that regularly help with PulseAudio issues.  Similar to your
experience, for me PulseAudio is mostly a "magic" thing which I tweak a bunch to
get what I need if I find I need something specific.

I'll try to be more help if I can.

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us

Bug#952302: marked as done (golang-github-docopt-docopt-go: FTBFS: failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: mkdir /sbuild-nonexistent: permission denied)

[Debian Bug Tracking System]

Your message dated Wed, 04 Mar 2020 01:51:46 +
with message-id 
and subject line Bug#952302: fixed in golang-github-docopt-docopt-go 
0.6.2+git20160216.0.784ddc5-2
has caused the Debian Bug report #952302,
regarding golang-github-docopt-docopt-go: FTBFS: failed to initialize build 
cache at /sbuild-nonexistent/.cache/go-build: mkdir /sbuild-nonexistent: 
permission denied
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.)


-- 
952302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-docopt-docopt-go
Version: 0.6.2+git20160216.0.784ddc5-1
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):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 
> github.com/docopt/docopt-go github.com/docopt/docopt-go/examples/arguments 
> github.com/docopt/docopt-go/examples/calculator 
> github.com/docopt/docopt-go/examples/config_file 
> github.com/docopt/docopt-go/examples/counted 
> github.com/docopt/docopt-go/examples/git 
> github.com/docopt/docopt-go/examples/git/branch 
> github.com/docopt/docopt-go/examples/git/checkout 
> github.com/docopt/docopt-go/examples/git/clone 
> github.com/docopt/docopt-go/examples/git/push 
> github.com/docopt/docopt-go/examples/git/remote 
> github.com/docopt/docopt-go/examples/naval_fate 
> github.com/docopt/docopt-go/examples/odd_even 
> github.com/docopt/docopt-go/examples/options 
> github.com/docopt/docopt-go/examples/options_shortcut 
> github.com/docopt/docopt-go/examples/quick 
> github.com/docopt/docopt-go/examples/type_assert
> internal/cpu
> internal/bytealg
> runtime/internal/atomic
> runtime/internal/sys
> runtime/internal/math
> runtime
> internal/reflectlite
> errors
> math/bits
> math
> unicode/utf8
> strconv
> internal/race
> sync/atomic
> sync
> unicode
> reflect
> sort
> internal/fmtsort
> io
> internal/oserror
> syscall
> time
> internal/poll
> internal/syscall/unix
> internal/testlog
> os
> fmt
> bytes
> strings
> regexp/syntax
> regexp
> github.com/docopt/docopt-go
> github.com/docopt/docopt-go/examples/arguments
> github.com/docopt/docopt-go/examples/calculator
> encoding
> encoding/binary
> encoding/base64
> unicode/utf16
> encoding/json
> github.com/docopt/docopt-go/examples/config_file
> github.com/docopt/docopt-go/examples/counted
> context
> path/filepath
> os/exec
> github.com/docopt/docopt-go/examples/git
> github.com/docopt/docopt-go/examples/git/branch
> github.com/docopt/docopt-go/examples/git/checkout
> github.com/docopt/docopt-go/examples/git/clone
> github.com/docopt/docopt-go/examples/git/push
> github.com/docopt/docopt-go/examples/git/remote
> github.com/docopt/docopt-go/examples/naval_fate
> github.com/docopt/docopt-go/examples/odd_even
> github.com/docopt/docopt-go/examples/options
> github.com/docopt/docopt-go/examples/options_shortcut
> github.com/docopt/docopt-go/examples/quick
> github.com/docopt/docopt-go/examples/type_assert
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> go test -v
> failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: 
> mkdir /sbuild-nonexistent: permission denied
> make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/02/22/golang-github-docopt-docopt-go_0.6.2+git20160216.0.784ddc5-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: golang-github-docopt-docopt-go
Source-Version: 0.6.2+git20160216.0.784ddc5-2
Done: Dmitry Smirnov 

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

Processed: Bug#952302 marked as pending in golang-github-docopt-docopt-go

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952302 [src:golang-github-docopt-docopt-go] 
golang-github-docopt-docopt-go: FTBFS: failed to initialize build cache at 
/sbuild-nonexistent/.cache/go-build: mkdir /sbuild-nonexistent: permission 
denied
Added tag(s) pending.

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

Bug#952302: marked as pending in golang-github-docopt-docopt-go

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #952302 in golang-github-docopt-docopt-go 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/go-team/packages/golang-github-docopt-docopt-go/-/commit/5155a8d61d8e865af9783e8ee0812a1607ca5075


rules: fixed testing (Closes: #952302).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952302

Bug#933425: sooperlooper: Please rebuild against wxWidgets GTK 3 package

[Steve Langasek]

Package: sooperlooper
Followup-For: Bug #933425
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

I've confirmed that sooperlooper can build against gtk3 with a one-line
change to the build-dependencies.  Please see attached.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru sooperlooper-1.7.3~dfsg0/debian/control 
sooperlooper-1.7.3~dfsg0/debian/control
--- sooperlooper-1.7.3~dfsg0/debian/control 2020-03-03 16:49:44.0 
-0800
+++ sooperlooper-1.7.3~dfsg0/debian/control 2020-03-03 17:00:41.0 
-0800
@@ -17,7 +17,7 @@
  libsamplerate-dev,
  libsigc++-2.0-dev (>= 2.2.10),
  libsndfile1-dev,
- libwxgtk3.0-dev,
+ libwxgtk3.0-gtk3-dev,
  libxml2-dev
 Standards-Version: 3.9.8
 Homepage: http://www.essej.net/sooperlooper/

Bug#953062: FTBFS on arm64, armel, armhf, ppc64el, s390x

[Ryan Pavlik]

arm64 and s390x (and maybe ppc64el?) are all an issue with signed char
conversions. I have a patch to fix that in my git repo, along with other
fixes that effectively block further usage (dfsg, etc):
https://salsa.debian.org/rpavlik-guest/meshlab/-/commit/2631636f29b7375a1d7977a1484b826db55ba153

armel and armhf: these platforms only have OpenGL-ES, not desktop
OpenGL, so the correct thing to do is to disable this package on those
platforms. Is there a better way to do this than to list all other
platforms in the control file?

Ryan

On 3/3/20 4:08 PM, Moritz Muehlenhoff wrote:
> Package: meshlab
> Severity: serious
>
> The new meshlab FTBFSes on arm64, armel, armhf, ppc64el, s390x.
>
> This also means that on those archs meshlab still uses Qt4.
>
> Cheers,
> Moritz
>



signature.asc
Description: OpenPGP digital signature

Processed: tagging 910930

[Debian Bug Tracking System]

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

> tags 910930 - buster + stretch
Bug #910930 {Done: Daniel Leidert } 
[ruby-factory-girl-rails] ruby-factory-girl-rails: installs files with generic 
names in /usr/bin
Removed tag(s) buster.
Bug #910930 {Done: Daniel Leidert } 
[ruby-factory-girl-rails] ruby-factory-girl-rails: installs files with generic 
names in /usr/bin
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Bug#952775: marked as done (Depends on projectm)

[Debian Bug Tracking System]

Your message dated Tue, 03 Mar 2020 22:35:38 +
with message-id 
and subject line Bug#952775: fixed in qmmp 1.3.1-1.1
has caused the Debian Bug report #952775,
regarding Depends on projectm
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.)


-- 
952775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qmmp-plugin-projectm
Severity: serious

projectm depends on Qt4, which is up for removal. qmmp in turn also depends on
projectm, so please drop the qmmp-plugin-projectm binary package.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: qmmp
Source-Version: 1.3.1-1.1
Done: Moritz Muehlenhoff 

We believe that the bug you reported is fixed in the latest version of
qmmp, 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.
Moritz Muehlenhoff  (supplier of updated qmmp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 03 Mar 2020 21:44:54 +0100
Source: qmmp
Architecture: source
Version: 1.3.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Matteo Cypriani 
Changed-By: Moritz Muehlenhoff 
Closes: 952775
Changes:
 qmmp (1.3.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop qmmp-plugin-projectm, projectm is being removed (Closes: #952775)
Checksums-Sha1:
 b5d297ef38ec97ba311146abe94b6957236f5eb5 2483 qmmp_1.3.1-1.1.dsc
 a70f4f3f60b89b5db28698d500ec058eacf17811 15544 qmmp_1.3.1-1.1.debian.tar.xz
 756d8e0f92fd502a225574fd3dd59380be3899b9 16571 qmmp_1.3.1-1.1_amd64.buildinfo
Checksums-Sha256:
 379ed295fb89a0879f6db48700b73256c3c2519d5eeb99fb8a7015b5e19e700d 2483 
qmmp_1.3.1-1.1.dsc
 b99e2a6e0388048e551be84a5a4d85ae686f168db65823680968d438e55689b6 15544 
qmmp_1.3.1-1.1.debian.tar.xz
 8270aba28db587052eb86baa109db864ba9e90c8377e9b802144b6a363c5fc96 16571 
qmmp_1.3.1-1.1_amd64.buildinfo
Files:
 162fc274dbf29970a421396ad111d8eb 2483 sound optional qmmp_1.3.1-1.1.dsc
 b7c9eb64c509cbd78a4a922c3e92b100 15544 sound optional 
qmmp_1.3.1-1.1.debian.tar.xz
 1dfb00f524929dbf969d494868bf4c15 16571 sound optional 
qmmp_1.3.1-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAl5e0poACgkQEMKTtsN8
TjZ3eQ/+Mfkqk7LtekcC21Ox8P+rjvwUiMj51s1Y6ycQrsm8hTxZqK5Xxvwkm2og
KDAcKfNeZZbWa3XfoIGPHAp7Qsz9yX46Ul7uDITmHrpKCXEujs3/SEcT7yqrJgYw
FyR2gRjFf8aYic9Yi2i0ihREaih7XMN9VvTGr/j62y/seeSQdTK9GgTNs/NIYSVC
ZMvpZEhUEuLmvkQvhG4hBqJCnHI83MRthcTnbQIRTjgDer3uaBPBH2RpLFm+x8Qr
aOK+efAV60mEbVstGp9Q1ieEinQWOooBxMixyom0WNLnTpPzydIfen/EnbXc0DUq
Bzkw3WIbBGLYDHVn94GIETnLeoJ63FC9AZlFcoRExG+EG9eTgzy4+L4njmeT6H8+
FVn1Yo+x3ThwIFMhzIKUpj83lDHbigP+ItTsAndacs1U2VH2neeq5jiWlFh5TTsK
CUHhcHlM1kDbE/zxLVc4OwcoS0O4pAJWNb5BLDKLZRxcjzymJgibgJVLxF0wfxlc
e/upbfIuE7BEmlGCU2tKUWS6dONw7aB6xHPaQrvixEFqizujJmlyz/4zAr/K0+Si
ldqiitQELp6zL93psJV6fhIqAlMeGVOxwxqWLNhqc1Kj+YOipfi/t2iTPssZ88xB
AWcLJTAtVjq+zBLnsQp2PKTBpDCQ5dWTSkg9qqd+VZ0IROWQMZU=
=10Fh
-END PGP SIGNATURE End Message ---

Bug#951608: marked as done (switchconf: Please make another source-only upload to allow testing migration)

[Debian Bug Tracking System]

Your message dated Tue, 03 Mar 2020 22:35:56 +
with message-id 
and subject line Bug#951608: fixed in switchconf 0.0.17-1
has caused the Debian Bug report #951608,
regarding switchconf: Please make another source-only upload to allow testing 
migration
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.)


-- 
951608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: switchconf
Version: 0.0.16-1
Severity: serious
Justification: out-of-sync unstable-to-testing

Dear switchconf maintainer,

The last upload of package switchconf was not a source-only upload. As a
result, the most recent upload will not migrate to Testing.

According to the policy of Release Team on Feb. 2020 [1], packages that are
out-of-sync between testing and unstable for more than 60 days are considered
to be having a Release-Critical bug.

Please make another source-only upload to solve this issue. For more
information, please see https://wiki.debian.org/SourceOnlyUpload .


[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html


-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: switchconf
Source-Version: 0.0.17-1
Done: Jose M Calhariz 

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

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

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

Debian distribution maintenance software
pp.
Jose M Calhariz  (supplier of updated switchconf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 03 Mar 2020 21:27:06 +
Source: switchconf
Architecture: source
Version: 0.0.17-1
Distribution: unstable
Urgency: medium
Maintainer: Jose M Calhariz 
Changed-By: Jose M Calhariz 
Closes: 951608
Changes:
 switchconf (0.0.17-1) unstable; urgency=medium
 .
   * Define debian/watch file.
   * Bug fix: "Please make another source-only upload to allow testing
 migration", thanks to Boyuan Yang (Closes: #951608).
   * Sign the tar.xz file when generating the distribution file.
Checksums-Sha1:
 cc887ba1676cdf856e8ea4f248c89ff36b602cf1 2106 switchconf_0.0.17-1.dsc
 774e53319c70562e949b9218cb31c88c225dc094 13172 switchconf_0.0.17.orig.tar.xz
 f4ee941a58cfbcbf1af0e90171b764f9734cecec 833 switchconf_0.0.17.orig.tar.xz.asc
 51238f49dc23151be9ed273d64c23443759080d3 345592 
switchconf_0.0.17-1.debian.tar.xz
 400d3b26370103b52d6a0a6c6ca846382a64f7fd 5882 
switchconf_0.0.17-1_source.buildinfo
Checksums-Sha256:
 4aa0e15010b10c14076bd82b03361bcc11624f68f90f174b7dc475d76aae7c04 2106 
switchconf_0.0.17-1.dsc
 3b425f84b40428b90e4a76b1e5264d9e5d0865e170f108769158f31ff0e7fe55 13172 
switchconf_0.0.17.orig.tar.xz
 922fd9ed517512ef74bbb9edc97ab5a7061a2643d0b11baf25a6d587373811bb 833 
switchconf_0.0.17.orig.tar.xz.asc
 cfada6bb015af8d92ff69f79b048bd0ad8159839ed34af7fe4ed1643cf7f2237 345592 
switchconf_0.0.17-1.debian.tar.xz
 1ec9f46cb0d9fe4bfacbcb126bc2bfa8ceabcc99a891f1a91cb1a244581e4a26 5882 
switchconf_0.0.17-1_source.buildinfo
Files:
 a7f08ff94e54389742bf2bffa497d04f 2106 admin optional switchconf_0.0.17-1.dsc
 7fa98062c4cf17a7e87c4990b7196f48 13172 admin optional 
switchconf_0.0.17.orig.tar.xz
 8303e882b750186bb80f2af5d93f908c 833 admin optional 
switchconf_0.0.17.orig.tar.xz.asc
 d4d95ea19700ee868894ea254f9a04ea 345592 admin optional 
switchconf_0.0.17-1.debian.tar.xz
 c9325528dfacfa883964cda6476617c0 5882 admin optional 
switchconf_0.0.17-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERkvHzUOf7l6LQJigNIp3jWiF748FAl5e1+8ACgkQNIp3jWiF
74+GFQ//X2rwMkzptV5St2Us0M6WjeQ9Avn1qOym96GNv4YI9oR7r/LQuvUTbeSO
j1ZgzvxpSz5wNnYTnbhZtf2gcKBchWXZmV+8mIL7Ij4BKx+iwg0yxPyGtNoU0mxb
iY1W+cYgl9ea1In6H5+1WMI2PmO8ohbSQUamlwwMAxpDTCisII2er93Joq0YLlSM
zrhXzU7oKogqjGQwGjGfmvHvyXa98kJtkPZyvYr6bQakq02bo/OG8lmQ2YBf1YQj
/wSWWRePRArbZ0L2F0PLGf20e+2OSOh9gqOneoYcGpEPci6ouk1GjxE8YnDmg+dc
VKCGf+DNjg2s5W3tO+EzSHQI/4F793CihKbe4nJuWsDWj5HqHUCmVs85DeqqjNAo
tjg/3H+dDz9Oxtg+TIRGCCycoiWVstRayC4l/2+5KN6JfujfB3XdMgBJMSwUQqgR

Bug#953064: FTBFS on i386

[Moritz Muehlenhoff]

Source: odin
Severity: serious

odin FTBFSes on i386. This also means that on i386 it still uses Qt4.

Cheers,
Moritz

Bug#953063: FTBFS on i386

[Moritz Muehlenhoff]

Source: mrtrix3
Severity: serious

mrtrix3 FTBFS on i386, which means that the stale i386 build still uses
Qt4.

There's the existing "#916284 mrtrix3 seems to be amd64-only", so I suggest
to simply restrict the arch list to amd64 and file an RM bug for the outdated
i386 binaries?

Cheers,
Moritz

Bug#953062: FTBFS on arm64, armel, armhf, ppc64el, s390x

[Moritz Muehlenhoff]

Package: meshlab
Severity: serious

The new meshlab FTBFSes on arm64, armel, armhf, ppc64el, s390x.

This also means that on those archs meshlab still uses Qt4.

Cheers,
Moritz

Bug#952893: marked as done (pycollada: Please make another source-only upload to allow testing migration)

[Debian Bug Tracking System]

Your message dated Tue, 03 Mar 2020 21:50:24 +
with message-id 
and subject line Bug#952893: fixed in pycollada 0.6-2
has caused the Debian Bug report #952893,
regarding pycollada: Please make another source-only upload to allow testing 
migration
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.)


-- 
952893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pycollada
Version: 0.6-1
Severity: serious
Justification: out-of-sync unstable-to-testing
X-Debbugs-CC: kkremit...@gmail.com kurt@kwk.systems ti...@debian.org

Dear package pycollada maintainers,

The latest upload of your package was not a source-only upload. As a result,
it did not migrate to Testing.

According to
https://lists.debian.org/debian-devel-announce/2020/02/msg5.html ,
packages that are out-of-sync between testing and unstable for more than 60
days are considered as having a Release Critical bug. Your package has been
out-of-sync for 140 days.

Please consider making another source-only upload to allow testing migration
according to https://wiki.debian.org/SourceOnlyUpload . Let me know if you
need any help. Thanks!

-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: pycollada
Source-Version: 0.6-2
Done: Kurt Kremitzki 

We believe that the bug you reported is fixed in the latest version of
pycollada, 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.
Kurt Kremitzki  (supplier of updated pycollada package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 02 Mar 2020 16:50:07 -0600
Source: pycollada
Architecture: source
Version: 0.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Kurt Kremitzki 
Closes: 952893
Changes:
 pycollada (0.6-2) unstable; urgency=medium
 .
   * [ed71f3f] Update to Standards Version 4.5.0 (no changes needed)
   * Make a new source-only upload (Closes: #952893)
Checksums-Sha1:
 5195c6033988e95b2cc8f39aa12c36931e4eff33 2141 pycollada_0.6-2.dsc
 b838739dc12b78916a118c36140796e5c557e229 3524 pycollada_0.6-2.debian.tar.xz
 fcb5505e9b47d8faefde22b7fa2ff9e81c7f2a17 9202 pycollada_0.6-2_source.buildinfo
Checksums-Sha256:
 2f3ab65becbdf58aa678b1d0bc908593d3f186773cfc4229db193f4560361f9e 2141 
pycollada_0.6-2.dsc
 1dfe788c97b95c763a05157128b6fa0e55842c67763f5bc6cfcf0364fc10280b 3524 
pycollada_0.6-2.debian.tar.xz
 6103dfea8e419142d5c445a21e67f989acf581a4baafba23771dc90a1d52ae29 9202 
pycollada_0.6-2_source.buildinfo
Files:
 adcb1629cdfe010453592d16a6fb9804 2141 libs optional pycollada_0.6-2.dsc
 4475c27a7fa36789a3cb49ef95ea85f8 3524 libs optional 
pycollada_0.6-2.debian.tar.xz
 78ba2569360f0e0b2f8541f7444ea2c2 9202 libs optional 
pycollada_0.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEh8RU7HmiYTD5HEfrKUghB0bfc8AFAl5ey+IRHGt1cnRAa3dr
LnN5c3RlbXMACgkQKUghB0bfc8C0tg//YeDs7QevwYyUKFhj8A4iyRWBt8G8vRmk
kWNpRC6TZefeGZu9VTwtY5jwDZ5tKd21KeiSxmvMFsPk6XZ1K+OXyrG4r9WhgMop
szJtn03YiVvN4I22RoTe+q9dV/t0/3HvM66f4yrwfDEaz27iaGBiV7Vt+ND+mj7m
bU5lLjG6eCTHvBEguUC5quDwaCpY+Puv7lC32LX+guvSmF5LoKkiXx54yI5uaMlv
ke/dTkVA5K2FtQRVNYGqC8WC0po5hwvU6INaLpGjXqCh8DpuEV/IsTKnem303vfV
L0jYUCZObfgqMYWyNsfK7XDvedro6EAcBaN1fWMaM9hvS33s+Plvb0K2eyw6bmaO
mzzeoJXXnDrwmPFczkPNugyLnsLhuSILeEEo6utOQBF7w/ZhqaSyNkKAOwN9sw1/
MtdVXH1WkIb6D9L1lBYIaMCcRg4+Ijkzjs8KgnjjWVwC+l871FAWZp5F+pI+lQ43
2vYNUJr7qgWjGp6CmDCaPVLp9vu1xW31/ZTMxjRaGMG20VUzhlVab1+PhpKuIrOz
MO70OTW02URXfBTSuZFE/1wMRCpmfkVgzXShwXM7MXdGBQR+yDJ2UjKRlu4WSEQx
eGM2SFl2pbVjeNXOla/byCViAkC+BUYWLBaS68zVqN7a4p0/4D0QQ+Y2ruj1gGPM
69PQu9J/TJc=
=UkFb
-END PGP SIGNATURE End Message ---

Bug#952188: marked as done (golang-github-mendersoftware-scopestack: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/mendersoftware/scopestack returned exit

[Debian Bug Tracking System]

Your message dated Tue, 03 Mar 2020 21:34:33 +
with message-id 
and subject line Bug#952188: fixed in golang-github-mendersoftware-scopestack 
0.0~git20180403.c2f5599-3
has caused the Debian Bug report #952188,
regarding golang-github-mendersoftware-scopestack: FTBFS: dh_auto_test: error: 
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/mendersoftware/scopestack 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.)


-- 
952188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-mendersoftware-scopestack
Version: 0.0~git20180403.c2f5599-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):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/mendersoftware/scopestack
> container/list
> runtime/internal/atomic
> internal/cpu
> runtime/internal/sys
> runtime/internal/math
> math/bits
> unicode/utf8
> internal/race
> sync/atomic
> unicode
> internal/bytealg
> math
> internal/testlog
> runtime
> internal/reflectlite
> sync
> errors
> sort
> io
> strconv
> internal/oserror
> syscall
> reflect
> internal/syscall/unix
> time
> internal/poll
> internal/fmtsort
> os
> fmt
> github.com/mendersoftware/scopestack
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/mendersoftware/scopestack
> === RUN   TestLicenses
> --- PASS: TestLicenses (0.00s)
> === RUN   TestPushPop
> --- PASS: TestPushPop (0.00s)
> === RUN   TestTooMuchPopping
> --- PASS: TestTooMuchPopping (0.00s)
> === RUN   TestPopInDefer
> --- PASS: TestPopInDefer (0.00s)
> === RUN   TestPushPopNotInSameFunction
> --- FAIL: TestPushPopNotInSameFunction (0.00s)
> scope_stack_test.go:57: Should never get here
> scope_stack_test.go:52: Pop() should have panicked when used in a 
> different function than Push()
> === RUN   TestDifferentScopeDistance
> --- FAIL: TestDifferentScopeDistance (0.00s)
> scope_stack_test.go:95: Should never get here
> scope_stack_test.go:89: Should have panicked because scope stack distance 
> should point to this function
> FAIL
> FAIL  github.com/mendersoftware/scopestack0.002s
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/mendersoftware/scopestack returned exit code 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/02/22/golang-github-mendersoftware-scopestack_0.0~git20180403.c2f5599-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: golang-github-mendersoftware-scopestack
Source-Version: 0.0~git20180403.c2f5599-3
Done: Andreas Henriksson 

We believe that the bug you reported is fixed in the latest version of
golang-github-mendersoftware-scopestack, 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.
Andreas Henriksson  (supplier of updated 
golang-github-mendersoftware-scopestack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 03 Mar 2020 06:50:53 +0100
Source: golang-github-mendersoftware-scopestack
Architecture: source
Version: 0.0~git20180403.c2f5599-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Andreas Henriksson 
Closes: 952188
Changes:
 

Bug#952188: marked as pending in golang-github-mendersoftware-scopestack

[Andreas Henriksson]

Control: tag -1 pending

Hello,

Bug #952188 in golang-github-mendersoftware-scopestack 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/go-team/packages/golang-github-mendersoftware-scopestack/-/commit/ca0b70274d2bd9ef26a8bf62edf5d2eaec8d7768


Add debian/patches/also-check-function-names.patch

Closes: #952188


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952188

Bug#952188: golang-github-mendersoftware-scopestack: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/mendersoftware/scopestack returned exit code 1

[Andreas Henriksson]

On Mon, Mar 02, 2020 at 09:38:00AM +0100, Lluis Campos wrote:
> Hello,
> 
> The patch looks good to us. Thanks Andreas for following up!
>
> Side note. We have discussed internally and decided that we will remove
> both scopestack and log[1] dependencies from the mender-client code.
> This will ease maintenance of the Debian package :)

Thanks for the feedback on the patch and the future roadmap!

I'll upload the patched scopestack for now and will be looking forward
to being able to request package removal later once new releases are
out and we have everything updated.

Regards,
Andreas Henriksson

Processed: Bug#952188 marked as pending in golang-github-mendersoftware-scopestack

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952188 [src:golang-github-mendersoftware-scopestack] 
golang-github-mendersoftware-scopestack: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/mendersoftware/scopestack returned exit code 1
Added tag(s) pending.

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

Bug#952610: fixed in meson 0.53.2-2

[Jussi Pakkanen]

On Mon, Mar 2, 2020 at 4:27 PM Gianfranco Costamagna
 wrote:

> lets see the sum of the issues without the stderr change
>
> amd64:
> crossbuild   FAIL stderr: dpkg-architecture: warning: specified GNU 
> system type arm-linux-gnueabihf does not match CC system type 
> powerpc64le-linux-gnu, try setting a correct CC environment variable

Can you test if the issue is fixed fro you if you add
stderr=subprocess.DEVNULL to debcrossgen line 38?

> > That should already be happening. AFAIUI the exhaustive test has a
> > dependency on all build deps of Meson, which includes valac and rustc.
> >
>
> nack on this. Fortunately there is a valac in unstable but not in testing, 
> and you can see there is no mention of meson autopkgtest against it.

That is strange, because if you look at the install log for Ubuntu tests:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/armhf/m/meson/20200303_171925_00939@/log.gz

both valac and rustc are installed. Maybe the autopkg dependency
lookup code gets confused by @builddeps@ somehow?

Bug#952714: texlive-latex-extra: missing Breaks+Replaces: sdaps (<< 1.9.7)

[Andreas Beckmann]

On 28/02/2020 01.14, Norbert Preining wrote:
> what on **EARTH** made sdaps install anything into /usr/share/texlive...

fortunately it's the only non-texlive package in buster doing this ...
(and none in sid does it)

grep -h usr/share/texlive lists/buster/Contents* | awk '{print $2}' |
sort | uniq -c | sort -n

Andreas

Processed: Re: Bug#953039: upgrading packet python3 up to 3.8.2-1 asks packets deletion

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #953039 [python3] upgrading packet python3 up to 3.8.2-1 asks packets 
deletion
Severity set to 'normal' from 'critical'

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

Bug#953039: upgrading packet python3 up to 3.8.2-1 asks packets deletion

[Matthias Klose]

Control: severity -1 normal

just wait until packages are installable again. It takes some time.

On 3/3/20 6:11 PM, Сергей Фёдоров wrote:
> 
> Package: python3
> Version: 3.7.5-3
> Severity: critical
> Tags: a11y
> Justification: breaks unrelated software
> 
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores)
> Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), 
> LANGUAGE=ru_RU.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages python3 depends on:
> ii  libpython3-stdlib  3.7.5-3
> ii  python3-minimal3.7.5-3
> ii  python3.7  3.7.6-1+b1
> 
> python3 recommends no packages.
> 
> Versions of packages python3 suggests:
> pn  python3-doc   
> pn  python3-tk
> pn  python3-venv  
> 
> -- no debconf information
> 
> Upgrading off package python3 from 3.7.5-3 to 3.8.2-1
> asks packets deletion:
> 
> hplip  3.20.2+dfsg0-1
> libreoffice  1:6.4.1-1
> libreoffice-librelogo  1:6.4.1-1
> libreoffice-script-provider-python  1:6.4.1-1
> libsmbclient  2:4.11.5+dfsg-1
> python3-smbc  1.0.15.6-2+b1
> python3-talloc  2.3.0-3
> python3-uno  1:6.4.1-1
> samba-libs  2:4.11.5+dfsg-1
> vlc-plugin-samba  3.0.8-4
> 
> but these are the latest versions of packages.
> 

Bug#952274: marked as pending in octave-queueing

[Rafael Laboissiere]

Control: tag -1 pending

Hello,

Bug #952274 in octave-queueing 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/pkg-octave-team/octave-queueing/-/commit/2ded09889d93d053e7637e051903cd7a766df16b


d/p/xseealso-texi2pdf.patch: New patch

This patch avoids a problem introduced with the introduction of macro
@seealso in Texinfo version 6.7, which clashes with the one defined in
Octave.

Gbp-Dch: Full
Closes: #952274


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952274

Processed: Bug#952274 marked as pending in octave-queueing

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952274 [src:octave-queueing] octave-queueing: FTBFS: error: writing file 
'/sbuild-nonexistent/.octave_hist': No such file or directory
Added tag(s) pending.

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

Bug#953040: prometheus-mysqld-exporter: Regression on configuration disallows proper use of mysql auth_socket authentication

[jynus]

Package: prometheus-mysqld-exporter
Version: 0.11.0+ds-1+b20
Severity: serious
Justification: Policy 10.9

Dear Maintainer,

After upgrading my MariaDB server boxes to buster, the version of
prometheus mysqld exporter monitoring package stopped working. When
I checked the cause of it, the package logged very usefuly the cause:

no user or password specified under [client] in /var/lib/prometheus/.my.s5.cnf

I checked an my [client] section had a user config, plust a password one, except
it was configured on purpose like this:

password = ''

I confirmed that by adding a fully random password, different from the empty 
string,
the exporter started working again.

This is because I use socket-based authentication for the prometheus mysqld
exporter user (https://mariadb.com/kb/en/authentication-plugin-unix-socket/),
something that is a best practice in a secure production environement.
In fact, Debian uses socket_auth for the default-created root user, which
makes Debian mariadb installation much more secure.

This issue not only forces users to maintain a password on the filesystem
in clear text (that can be easily stolen or leaked by accident, and reused
for other similarly-configured systems), it overpases the additional checks
of socket-auth, that requires a matching unix acccount with the same name
as that of the mysql account.

This is a regression because auth_socket was working properly on previous
versions of prometheus available on stretch and other OSs. Not only this
breaks existing installations, it also discourages the usage of the avobe
mentioned, more secure authentication mechanism.

If UI-friendly errors are prefered (because people forgets to create or
protect mysql accounts, please allow me to specifically mark "this account
doesn't have a password, and I know what I am doing".

I have not reported this upstream.


-- System Information:
Debian Release: 10.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages prometheus-mysqld-exporter depends on:
ii  daemon  0.6.4-1+b2
ii  libc6   2.28-10

prometheus-mysqld-exporter recommends no packages.

Versions of packages prometheus-mysqld-exporter suggests:
pn  default-mysql-server | virtual-mysql-server  

-- no debconf information

Bug#953039: upgrading packet python3 up to 3.8.2-1 asks packets deletion

[Сергей Фёдоров]

Package: python3
Version: 3.7.5-3
Severity: critical
Tags: a11y
Justification: breaks unrelated software



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

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

Versions of packages python3 depends on:
ii  libpython3-stdlib  3.7.5-3
ii  python3-minimal3.7.5-3
ii  python3.7  3.7.6-1+b1

python3 recommends no packages.

Versions of packages python3 suggests:
pn  python3-doc   
pn  python3-tk
pn  python3-venv  

-- no debconf information

Upgrading off package python3 from 3.7.5-3 to 3.8.2-1
asks packets deletion:

hplip  3.20.2+dfsg0-1
libreoffice  1:6.4.1-1
libreoffice-librelogo  1:6.4.1-1
libreoffice-script-provider-python  1:6.4.1-1
libsmbclient  2:4.11.5+dfsg-1
python3-smbc  1.0.15.6-2+b1
python3-talloc  2.3.0-3
python3-uno  1:6.4.1-1
samba-libs  2:4.11.5+dfsg-1
vlc-plugin-samba  3.0.8-4

but these are the latest versions of packages.

Processed: Python 3.8 is now the default, raising severity of python3.8 issues

[Debian Bug Tracking System]

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

> severity 942735 serious
Bug #942735 [src:python-persistent] rules snippet to move the include directory 
is not valid shell script and breaks with Python 3.8
Ignoring request to change severity of Bug 942735 to the same value.
> severity 943334 serious
Bug #943334 [src:dh-python] please run the tests for all supported python 
versions
Severity set to 'serious' from 'important'
> severity 943495 serious
Bug #943495 [src:setools] fix building with a new compiler warning when 
building for python3.8
Severity set to 'serious' from 'important'
> severity 943627 serious
Bug #943627 [src:libcap-ng] libcap-ng: b-d on python3-all-dev, but not built 
for all supported Python3 versions
Severity set to 'serious' from 'normal'
> severity 943631 serious
Bug #943631 [src:coda] coda: b-d on python3-all-dev, but not built for all 
supported Python3 versions
Severity set to 'serious' from 'normal'
> severity 943633 serious
Bug #943633 [src:cmor] cmor: b-d on python3-all-dev, but not built for all 
supported Python3 versions
Severity set to 'serious' from 'normal'
> severity 943636 serious
Bug #943636 [src:uhd] uhd: b-d on python3-all-dev, but not built for all 
supported Python3 versions
Severity set to 'serious' from 'normal'
> severity 943966 serious
Bug #943966 [python3-freezegun] cookiecutter: failing tests with python3.8
Bug #944026 [python3-freezegun] freezegun: failing tests with python3.8
Ignoring request to change severity of Bug 943966 to the same value.
Ignoring request to change severity of Bug 944026 to the same value.
> severity 945327 serious
Bug #945327 [src:python-pomegranate] python-pomegranate ftbfs in unstable
Ignoring request to change severity of Bug 945327 to the same value.
> severity 945411 serious
Bug #945411 [src:pyfai] pyfai fails tests with Python 3.8
Ignoring request to change severity of Bug 945411 to the same value.
> severity 948016 serious
Bug #948016 [src:fontforge] fontforge: b-d on python3-all-dev, but not built 
for all supported Python3 versions
Severity set to 'serious' from 'normal'
> severity 948018 serious
Bug #948018 [src:getfem++] getfem++: b-d on python3-all-dev, but not built for 
all supported Python3 versions
Severity set to 'serious' from 'normal'
> severity 948020 serious
Bug #948020 [src:stimfit] stimfit: b-d on python3-all-dev, but not built for 
all supported Python3 versions
Severity set to 'serious' from 'normal'
> severity 948320 serious
Bug #948320 [dh-python] pybuild hard codes the m modifier now dropped in Python 
3.8
Ignoring request to change severity of Bug 948320 to the same value.
> severity 949793 serious
Bug #949793 [src:d-shlibs] dh-shlibs fails for Python 3.8 libs
Severity set to 'serious' from 'important'
> severity 949822 serious
Bug #949822 [src:fontforge] fontforge needs to link with the embedded libs
Severity set to 'serious' from 'important'
> severity 949835 serious
Bug #949835 [src:lirc] lirc ftbfs with python 3.8
Ignoring request to change severity of Bug 949835 to the same value.
> severity 950147 serious
Bug #950147 [src:sagemath] sagemath ftbfs with python 3.8
Severity set to 'serious' from 'important'
> severity 950210 serious
Bug #950210 [src:python-opcua] autopkg test failure with python3.8
Severity set to 'serious' from 'important'
> severity 950221 serious
Bug #950221 [src:natsort] natsort 6.0 doesn't support Python 3.8
Ignoring request to change severity of Bug 950221 to the same value.
> severity 950222 serious
Bug #950222 [src:pyavm] autopkg test fails with output on stderr
Severity set to 'serious' from 'important'
> severity 950234 serious
Bug #950234 [src:freezegun] don't hard-code an upper limit on the python version
Ignoring request to change severity of Bug 950234 to the same value.
> severity 950839 serious
Bug #950839 [src:reprounzip] reprounzip autopkg test fails with python 3.8
Severity set to 'serious' from 'normal'
> severity 950842 serious
Bug #950842 [src:qiime] autopkg tests fail with Python 3.8
Severity set to 'serious' from 'important'
> severity 950847 serious
Bug #950847 [src:python-icecream] python-icecream needs new upstream for Python 
3.8 support
Ignoring request to change severity of Bug 950847 to the same value.
> severity 950858 serious
Bug #950858 [src:fades] fades fails autopkg tests with python 3.8
Severity set to 'serious' from 'important'
> severity 950860 serious
Bug #950860 [src:sfepy] sfepy fails build2 autopkg test with python 3.8
Severity set to 'serious' from 'important'
> severity 951706 serious
Bug #951706 [src:gdspy] gdspy hard-codes python3.7, without depending on it
Ignoring request to change severity of Bug 951706 to the same value.
> severity 951707 serious
Bug #951707 [src:gringo] gringo ftbfs with Python 3.8
Severity set to 'serious' from 'important'
> severity 951768 serious
Bug #951768 [src:skimage] skimage documentation build fails with python 3.8
Severity set to 'serious' from 'important'
> severity 951829 serious
Bug #951829 

Bug#950983: clickhouse FTBFS in bullseye/sid

[Stefano Rivera]

Hi Jochen (2020.02.09_00:40:36_-0800)

Control: tag -1 + patch

I notice that Ubuntu has a patch for this:
https://launchpadlibrarian.net/466815449/clickhouse_18.16.1+ds-5_18.16.1+ds-5ubuntu1.diff.gz

It's building on amd64 and ppc64el:
https://launchpad.net/ubuntu/+source/clickhouse/18.16.1+ds-5ubuntu1

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Processed: tagging 951960, tagging 949280

[Debian Bug Tracking System]

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

> tags 951960 + experimental
Bug #951960 {Done: michael.cru...@gmail.com (Michael R. Crusoe)} 
[libspdlog-dev] purify: FTBFS: ld: ../purify/libpurify.so.2.0.0: undefined 
reference to `fmt::v6::internal::basic_data::signs'
Bug #951995 {Done: michael.cru...@gmail.com (Michael R. Crusoe)} 
[libspdlog-dev] sopt: FTBFS: core.h:266: undefined reference to 
`fmt::v6::internal::assert_fail(char const*, int, char const*)'
Bug #952543 {Done: michael.cru...@gmail.com (Michael R. Crusoe)} 
[libspdlog-dev] Using old libfmt breaks sopt and purify
Added tag(s) experimental.
Added tag(s) experimental.
Added tag(s) experimental.
> tags 949280 + experimental
Bug #949280 {Done: Jelmer Vernooij } [src:breezy] breezy 
fails it's autopkg tests on arm64
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Bug#952107: marked as done (valabind: FTBFS: ../gowriter.vala:217.16-217.26: error: The name `data_type' does not exist in the context of `Vala.DataType' (libvala-0.48))

[Debian Bug Tracking System]

Your message dated Tue, 03 Mar 2020 16:31:47 +
with message-id 
and subject line Bug#952107: fixed in valabind 1.7.1-5
has caused the Debian Bug report #952107,
regarding valabind: FTBFS: ../gowriter.vala:217.16-217.26: error: The name 
`data_type' does not exist in the context of `Vala.DataType' (libvala-0.48)
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.)


-- 
952107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: valabind
Version: 1.7.1-4
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):
> DC-Build-Header: valabind 1.7.1-4 / 2020-02-23 02:51:43 +
> DC-Task: type:rebuild-full source:valabind version:1.7.1-4 chroot:unstable 
> esttime:34 logfile:/tmp/valabind_1.7.1-4_unstable.log modes:
> DC-Sbuild-call: su user42 -c 'sbuild -n -A -s --force-orig-source 
> --apt-update -d unstable -v  valabind_1.7.1-4'
> sbuild (Debian sbuild) 0.78.1 (09 February 2019) on 
> ip-172-31-0-235.eu-central-1.compute.internal
> 
> +==+
> | valabind 1.7.1-4 (amd64) Sun, 23 Feb 2020 02:51:43 
> + |
> +==+
> 
> Package: valabind
> Version: 1.7.1-4
> Source Version: 1.7.1-4
> Distribution: unstable
> Machine Architecture: amd64
> Host Architecture: amd64
> Build Architecture: amd64
> Build Type: full
> 
> I: NOTICE: Log filtering will replace 
> 'var/run/schroot/mount/sid-amd64-sbuild-c5248c31-2528-48b7-b7b8-dc9525a33acc' 
> with '<>'
> I: NOTICE: Log filtering will replace 'build/valabind-wKtnT7/resolver-dcf8rt' 
> with '<>'
> 
> +--+
> | Update chroot   
>  |
> +--+
> 
> Get:1 http://127.0.0.1:/debian sid InRelease [142 kB]
> Get:2 http://127.0.0.1:/debian sid/main Sources.diff/Index [27.9 kB]
> Get:3 http://127.0.0.1:/debian sid/main amd64 Packages.diff/Index [27.9 
> kB]
> Get:4 http://127.0.0.1:/debian sid/main Sources 2020-02-22-1413.16.pdiff 
> [14.3 kB]
> Get:5 http://127.0.0.1:/debian sid/main Sources 2020-02-22-2013.35.pdiff 
> [18.5 kB]
> Get:5 http://127.0.0.1:/debian sid/main Sources 2020-02-22-2013.35.pdiff 
> [18.5 kB]
> Get:6 http://127.0.0.1:/debian sid/main amd64 Packages 
> 2020-02-22-1413.16.pdiff [13.0 kB]
> Get:7 http://127.0.0.1:/debian sid/main amd64 Packages 
> 2020-02-22-2013.35.pdiff [10.6 kB]
> Get:7 http://127.0.0.1:/debian sid/main amd64 Packages 
> 2020-02-22-2013.35.pdiff [10.6 kB]
> Fetched 255 kB in 1s (243 kB/s)
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Calculating upgrade...
> The following packages will be upgraded:
>   binutils binutils-common binutils-x86-64-linux-gnu libbinutils libctf-nobfd0
>   libctf0
> 6 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 4327 kB of archives.
> After this operation, 1024 B of additional disk space will be used.
> Get:1 http://127.0.0.1:/debian sid/main amd64 libctf0 amd64 2.34-3 [45.7 
> kB]
> Get:2 http://127.0.0.1:/debian sid/main amd64 libctf-nobfd0 amd64 2.34-3 
> [101 kB]
> Get:3 http://127.0.0.1:/debian sid/main amd64 binutils amd64 2.34-3 [58.9 
> kB]
> Get:4 http://127.0.0.1:/debian sid/main amd64 binutils-x86-64-linux-gnu 
> amd64 2.34-3 [1587 kB]
> Get:5 http://127.0.0.1:/debian sid/main amd64 libbinutils amd64 2.34-3 
> [472 kB]
> Get:6 http://127.0.0.1:/debian sid/main amd64 binutils-common amd64 
> 2.34-3 [2063 kB]
> debconf: delaying package configuration, since apt-utils is not installed
> Fetched 4327 kB in 0s (97.3 MB/s)
> (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 

Processed: python-xarray: autopkgtest regression

[Debian Bug Tracking System]

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

> reassign 935455 src:python-xarray 0.12.3-1
Bug #935455 [python-xarray] python-xarray: autopkgtest regression: test_dask 
fails
Bug reassigned from package 'python-xarray' to 'src:python-xarray'.
Ignoring request to alter found versions of bug #935455 to the same values 
previously set
Ignoring request to alter fixed versions of bug #935455 to the same values 
previously set
Bug #935455 [src:python-xarray] python-xarray: autopkgtest regression: 
test_dask fails
Marked as found in versions python-xarray/0.12.3-1.
> retitle 935455 python-xarray: autopkgtest regression
Bug #935455 [src:python-xarray] python-xarray: autopkgtest regression: 
test_dask fails
Changed Bug title to 'python-xarray: autopkgtest regression' from 
'python-xarray: autopkgtest regression: test_dask fails'.
> thanks
Stopping processing here.

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

Bug#952695: Request for sponsorship or upload rights Re: r-cran-xml2: autopkgtest failure against libxml2 2.9.10

[Michael R. Crusoe]

On Thu, 27 Feb 2020 19:20:06 +0100 Mattia Rizzolo  wrote:
> Source: r-cran-xml2
> Version: 1.2.2-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: breaks needs-update
>
> Dear maintainer,
>
> With a recent upload of libxml2 the autopkgtest of r-cran-xml2 fails
> in testing when that autopkgtest is run with the binary packages of
> libxml2 from unstable. It passes when run with only packages from
> testing.


Hello,

At 
https://salsa.debian.org/r-pkg-team/r-cran-xml2/-/commit/e973a8d9500dc3a98e34dcd5eb7e86cf5b692bb6 
I've commited a fix for this bug.



If a DD could sponsor that upload or grant me upload rights, I would 
appreciate it.



gbp clone g...@salsa.debian.org:r-pkg-team/r-cran-xml2.git


or


dcut dm --uid 724D609337113C710550D7473C26763F6C67E6E2 --allow r-cran-xml2


Cheers,

Bug#953028: node-nodedbi: Not compatible with Node.js ≥ 12

[Xavier Guimard]

Package: node-nodedbi
Severity: grave
Tags: upstream
Justification: renders package unusable

Hi,

node-nodedbi is not compatible with Node.js ≥ 12. This RC bug will
permit to remove this (useless for now) package from testing to permit
Node.js 12 migration.

Bug#936630: marked as done (gnumed-client: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 03 Mar 2020 14:47:23 +
with message-id 
and subject line Bug#936630: fixed in gnumed-client 1.8.0+dfsg-1
has caused the Debian Bug report #936630,
regarding gnumed-client: 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.)


-- 
936630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnumed-client
Version: 1.7.6+dfsg-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:gnumed-client

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: gnumed-client
Source-Version: 1.8.0+dfsg-1
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated gnumed-client package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 03 Mar 2020 15:08:17 +0100
Source: gnumed-client
Architecture: source
Version: 1.8.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 936630 952633
Changes:
 gnumed-client (1.8.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream version
 Closes: #936630
   * Freediams was removed from Debian so Recommends is not appropriate
 any more and freediams was moved to Suggests
   * Standards-Version: 4.5.0 (routine-update)
   * Add salsa-ci file (routine-update)
   * Wrap long lines in changelog entries: 0.2.7.0-1, 20030619-1.
   * Use secure URI in Homepage field.
   * Set upstream metadata fields: Repository, Repository-Browse.
   * Follow hints from upstream regarding changed depends and installation
 of files
 Closes: #952633
   * Lintian-override for appstream metadata license
Checksums-Sha1:
 

Bug#949919: marked as done (libgpiod: ftbfs; needs explicit dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Tue, 03 Mar 2020 14:49:52 +
with message-id 
and subject line Bug#949919: fixed in libgpiod 1.4.1-4
has caused the Debian Bug report #949919,
regarding libgpiod: ftbfs; needs explicit dependency on dh-python
to be marked as done.

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

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


-- 
949919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgpiod
Version: 1.4.1-3
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

Hi, the package fails to build in sid. It now needs an explicit
dependency on dh-python. I'll attach a patch, but really: it's trivial.

Cheers,
mwh

-- System Information:
Debian Release: buster/sid
  APT prefers eoan-updates
  APT policy: (500, 'eoan-updates'), (500, 'eoan'), (400, 'eoan-proposed'), 
(100, 'eoan-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-26-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libgpiod-1.4.1/debian/changelog libgpiod-1.4.1/debian/changelog
--- libgpiod-1.4.1/debian/changelog 2019-09-10 21:02:05.0 +1200
+++ libgpiod-1.4.1/debian/changelog 2020-01-27 14:14:51.0 +1300
@@ -1,3 +1,9 @@
+libgpiod (1.4.1-4) UNRELEASED; urgency=medium
+
+  * Add explicit build dependency on dh-python.
+
+ -- Michael Hudson-Doyle   Mon, 27 Jan 2020 14:14:51 +1300
+
 libgpiod (1.4.1-3) unstable; urgency=medium
 
   * d/control:
diff -Nru libgpiod-1.4.1/debian/control libgpiod-1.4.1/debian/control
--- libgpiod-1.4.1/debian/control   2019-09-10 20:50:54.0 +1200
+++ libgpiod-1.4.1/debian/control   2020-01-27 14:13:09.0 +1300
@@ -5,6 +5,7 @@
 Build-Depends: debhelper-compat (= 12),
autoconf-archive,
automake,
+   dh-python,
help2man,
pkg-config,
m4,
--- End Message ---
--- Begin Message ---
Source: libgpiod
Source-Version: 1.4.1-4
Done: =?utf-8?b?U1ogTGluICjmnpfkuIrmmbop?= 

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

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

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

Debian distribution maintenance software
pp.
SZ Lin (林上智)  (supplier of updated libgpiod package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 03 Mar 2020 21:46:43 +0800
Source: libgpiod
Architecture: source
Version: 1.4.1-4
Distribution: unstable
Urgency: medium
Maintainer: SZ Lin (林上智) 
Changed-By: SZ Lin (林上智) 
Closes: 949919 949958 951196 951197
Changes:
 libgpiod (1.4.1-4) unstable; urgency=medium
 .
   * Fix symbols disappeared on s390x - Thanks to Gianfranco Costamagna
  (Closes: #949958)
   * Add Multi-Arch attribute - Thanks to Helmut Grohne 
 (Closes: #951196)
   * Support nopython build profile to avoid FTFBS issue - This patch was
 tweaked from Helmut Grohne . Thanks the report from
 Michael Hudson-Doyle (Closes:#949919, #951197)
   * d/control:
 - Bump Standards-Version to 4.5.0
 - Set Rules-Requires-Root: no
   * d/watch:
 - Ignore watching on rc version
Checksums-Sha1:
 b219ce88282929169f882b38f28e37e2d33fdaa5 2294 libgpiod_1.4.1-4.dsc
 2e12af6fe82c80bf8d125c3dd185c668e48131e8 6132 libgpiod_1.4.1-4.debian.tar.xz
 2fa9a3e75b17b7f295ef00a0c276c56765d327c6 8593 libgpiod_1.4.1-4_amd64.buildinfo
Checksums-Sha256:
 72d03be24e448c284223c925d732df839c90fc276c51037ff069fd561cee853f 2294 
libgpiod_1.4.1-4.dsc
 ce0c04b1771130383cffac452c3fab914ea19916a210897bce268f9528722dad 6132 
libgpiod_1.4.1-4.debian.tar.xz
 19d5e098e0365118d40540d94ad440fe776127db3c8e0beba7bc54868c48e390 8593 
libgpiod_1.4.1-4_amd64.buildinfo
Files:
 fe13f2e4ad32cfb3b6c4a96587678814 2294 misc optional libgpiod_1.4.1-4.dsc
 4138f74c83d93e7bf9cd09ce66d4e4c7 6132 misc optional 
libgpiod_1.4.1-4.debian.tar.xz
 

Bug#944769: python3-h5py fails to import if offline due to apparent MPI failure

[Thibaut Paumard]

Hi again,

Le 03/03/2020 à 11:55, Drew Parsons a écrit :

>> Actually, it may be wise to choose names that
>>
>>   a) are clearly private, so people know they should not start using
>> explicitly h5py_serial or h5py_mpi;
>>
>>   b) will not clash with anything upstream may adopt in the future, a
>> bit like choosing a debian-specific soname for  shared library.
>>
>> why not _debian_h5py_serial and _debian_h5py_mpi?
>>
> 
> 
> Actually I was thinking people could start using h5py_serial or
> h5py_mpi, then they'd be sure of exactly what they're getting.
> 
> But I can see your point.  It wouldn't be so portable if users started
> doing that.

Yep, people can still use _debian_h5py_mpi to be sure of what they get,
but it is clear to them that they enter non-portable territory.

> If we want to present it as _debian*, then I think it would be tidier to
> place these _debian dir underneath h5py.  That layout could be even
> better for upstream since they'd want to do likewise (_h5py_serial,
> _h5py_mpi under h5py), if they take up this suggestion.
> 

Yes, I kinda like h5py._debian.serial and h5py._debian.mpi. Looks tidy
an future-proof.

Regards, Thibaut.





signature.asc
Description: OpenPGP digital signature

Bug#945442: Possible to backspace past beginning of string, which appears to be identical to having pressed Enter immediately, without any backspace

[Marvin Renich]

* Joerg Dorchain  [200303 05:15]:
> On Tue, Mar 03, 2020 at 10:57:41AM +0100, Andras Korn wrote:
> > I filed https://github.com/neomutt/neomutt/issues/2161.
> 
> Thanks for the effort, but:
> 
> Duplicate #2002 and there's already pull request for it #2160.
> @gahr gahr closed this 6 minutes ago 
> 
> Looks like cherry-pikcing that patch and thinking about the default setting.

No, #2002 is _not_ the same.  See my previous message.

Neomutt bug #2002 is about editing headers.  This Debian bug and Neomutt
#2161 are about commands in the message index.  The behaviors are
different in the two situations.

There are three behaviors being discussed:

1. old behavior:  backspace stays on the command line
2. new behavior:  backspace aborts the command
3. wrong behavior:  backspace invokes command with default argument

In #2002, while editing headers, you currently get "new behavior".  The
bug reporter wants "old behavior" (what the previous version of Neomutt
did in this situation).  The patch adds a config option to select which
you want.

In #2161, while in the message index, the previous version of Neomutt
gave "old behavior".  The current Neomutt gives "wrong behavior", _not_
"new behavior".

For example, type s and (assuming a save-hook matches for the message)
the command line shows:

Save to mailbox ('?' for list): +some_folder

Now keep backspacing until +some_folder is gone and backspace one more
time.  Instead of aborting the save, the message is actually saved to
+some_folder!  This is really, _really_ wrong!

First, #2161 must be fixed so it doesn't give "wrong behavior".  Then,
the patch needs to be tested to see if it affects both editing message
headers (#2002) and commands in the message index (#2161).  If it does,
great!  If it doesn't, the patch should be updated so that it does.

Then, the default needs to be decided.

Holding the backspace key down is common practice for some people as a
way of erasing the default prompt in preparation for typing a different
value.

Both for this reason and to reduce surprise and change, I feel that the
default should be "old behavior", but I can live with setting the option
myself if other people would rather have "new behavior" as the default.

There is one more reason that having backspace remain on the command
line instead of aborting is a better default.  If someone has bound the
backspace key to some action in the message index (or in the message
editing screen), holding down the backspace key could invoke the bound
action on one (or several) messages in the index, depending on how
quickly the user releases the key.

...Marvin

Bug#953008:

[Andreas Hasenack]

PR up at https://salsa.debian.org/samba-team/talloc/-/merge_requests/7

Bug#952306: marked as done (freelan: FTBFS: AttributeError: 'str' object has no attribute 'decode':)

[Debian Bug Tracking System]

Your message dated Tue, 03 Mar 2020 12:34:52 +
with message-id 
and subject line Bug#952306: fixed in freelan 2.2-3
has caused the Debian Bug report #952306,
regarding freelan: FTBFS: AttributeError: 'str' object has no attribute 
'decode':
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.)


-- 
952306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freelan
Version: 2.2-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[1]: Entering directory '/<>'
> FREELAN_NO_GIT=1 FREELAN_NO_GIT_VERSION=2.2 scons -c --mode=release apps 
> prefix=/ bin_prefix=/usr/ --upnp=yes --mongoose=no
> scons: Reading SConscript files ...
> AttributeError: 'str' object has no attribute 'decode':
>   File "/<>/SConstruct", line 219:
> libraries, includes, apps, samples, configurations, help = 
> SConscript('SConscript', exports='env', variant_dir=os.path.join('build', 
> env.mode))
>   File "/usr/lib/scons/SCons/Script/SConscript.py", line 660:
> return method(*args, **kw)
>   File "/usr/lib/scons/SCons/Script/SConscript.py", line 597:
> return _SConscript(self.fs, *files, **subst_kw)
>   File "/usr/lib/scons/SCons/Script/SConscript.py", line 286:
> exec(compile(scriptdata, scriptname, 'exec'), call_stack[-1].globals)
>   File "/<>/build/release/SConscript", line 28:
> env.GenerateDefines(target=os.path.join('include', 
> env.defines.defines_file_name), source=env.defines.template_file_path)
>   File "/<>/defines.py", line 94:
> return os.path.splitext(os.path.basename(self.template_file_path))[0]
>   File "/<>/defines.py", line 90:
> return os.path.join(self.repository_root, 'defines.hpp.template')
>   File "/<>/defines.py", line 46:
> return self._repository_root.decode('utf-8')
> make[1]: *** [Makefile:24: clean] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/freelan_2.2-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: freelan
Source-Version: 2.2-3
Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= 

We believe that the bug you reported is fixed in the latest version of
freelan, 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.
Håvard Flaget Aasen  (supplier of updated freelan 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 29 Feb 2020 15:56:31 +0100
Source: freelan
Architecture: source
Version: 2.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Håvard Flaget Aasen 
Closes: 952306
Changes:
 freelan (2.2-3) unstable; urgency=medium
 .
   * QA Upload.
   * Update Standards-Version to 4.5.0
   * Add Rules-Requires-Root: no
   * Add folder to d/clean
   * Set upstream metadata fields: Bug-Database, Repository,
 Repository-Browse, Bug-Submit.
   * Add upstream commit as 0007-Move-to-Python-3.patch
   * Add upstream commit as 0006-Fix-build-outside-git.patch closes: #952306
Checksums-Sha1:
 ff8065a9879254f6d35dfb27aaa9fa68280b2d42 1977 freelan_2.2-3.dsc
 c3e442b310c2e376e38de17bfac0281dbd09e42a 12044 freelan_2.2-3.debian.tar.xz
 8339674594a42ee7b1e2bb51805c510cbcad893b 7582 freelan_2.2-3_source.buildinfo
Checksums-Sha256:
 847e3c4a7d6e6d27afcc35dff9502b582a639419f7f0dd234e3f2b4a9718e316 1977 
freelan_2.2-3.dsc
 c10f6081ceb6c166a4278b643b67cc9670ff976f2ea81bedfdb2496d6e520a3a 12044 
freelan_2.2-3.debian.tar.xz
 425a70dc3dcb9deb2aeaef9d92bbbd0aa347e3dd7efe0f6053afa9767d99 7582 
freelan_2.2-3_source.buildinfo
Files:
 b36cbaef89df98724a27db5589586c28 1977 

Bug#952076: closing 952076

[Antonio Terceiro]

close 952076 3.0.8-1
thanks

this has been fixed in the latest upload, but I missed closing this bug.

Processed: closing 952076

[Debian Bug Tracking System]

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

> close 952076 3.0.8-1
Bug #952076 [src:ruby-mixlib-log] ruby-mixlib-log: FTBFS: ERROR: Test "ruby2.7" 
failed: Failure/Error: expect(opened_files_count_after).to 
eq(opened_files_count_before + 1)
Marked as fixed in versions ruby-mixlib-log/3.0.8-1.
Bug #952076 [src:ruby-mixlib-log] ruby-mixlib-log: FTBFS: ERROR: Test "ruby2.7" 
failed: Failure/Error: expect(opened_files_count_after).to 
eq(opened_files_count_before + 1)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#944769: python3-h5py fails to import if offline due to apparent MPI failure

[Drew Parsons]

On 2020-03-03 18:40, Thibaut Paumard wrote:

Hi Drew,

Le 02/03/2020 à 17:33, Drew Parsons a écrit :

Like you, I would keep h5py_serial and h5py_mpi separate rather than
submodules of h5py. Mostly because the h5py folks could in the future
want to use those two names and do it in an incompatible manner.


Fair enough, I'll keep them separate. (actually, I'll file an Issue
upstream and let them know what we've done. They may want to adapt for
themselves).


Actually, it may be wise to choose names that

  a) are clearly private, so people know they should not start using
explicitly h5py_serial or h5py_mpi;

  b) will not clash with anything upstream may adopt in the future, a
bit like choosing a debian-specific soname for  shared library.

why not _debian_h5py_serial and _debian_h5py_mpi?




Actually I was thinking people could start using h5py_serial or 
h5py_mpi, then they'd be sure of exactly what they're getting.


But I can see your point.  It wouldn't be so portable if users started 
doing that.


If we want to present it as _debian*, then I think it would be tidier to 
place these _debian dir underneath h5py.  That layout could be even 
better for upstream since they'd want to do likewise (_h5py_serial, 
_h5py_mpi under h5py), if they take up this suggestion.


Drew

Bug#944769: python3-h5py fails to import if offline due to apparent MPI failure

[Thibaut Paumard]

Hi Drew,

Le 02/03/2020 à 17:33, Drew Parsons a écrit :
>> Like you, I would keep h5py_serial and h5py_mpi separate rather than
>> submodules of h5py. Mostly because the h5py folks could in the future
>> want to use those two names and do it in an incompatible manner.
> 
> Fair enough, I'll keep them separate. (actually, I'll file an Issue
> upstream and let them know what we've done. They may want to adapt for
> themselves).

Actually, it may be wise to choose names that

  a) are clearly private, so people know they should not start using
explicitly h5py_serial or h5py_mpi;

  b) will not clash with anything upstream may adopt in the future, a
bit like choosing a debian-specific soname for  shared library.

why not _debian_h5py_serial and _debian_h5py_mpi?

Feel free to disregard this suggestion or choose something else as you
see fit. Just my 2c to avoid future headaches.

Regards, Thibaut.






signature.asc
Description: OpenPGP digital signature

Bug#953010: glade: Upgrade to 3.22.2 ( to work with libglib2 >= 2.63.2 )

[Simon McVittie]

On Tue, 03 Mar 2020 at 08:47:56 +, Simon McVittie wrote:
> From codesearch.debian.net, similar fixes might be needed in
> [some packages]

Sorry, I was misreading the commit.

This bug is about a property with a space in it, which was never
considered to be valid (but was accepted anyway, until recently).

The packages I listed use property names with underscores, which are
allowed and canonicalized to "-". Performance will be slightly better
if they are fixed, but underscores are documented to be OK.

smcv

Processed: block 953002 with 951087

[Debian Bug Tracking System]

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

> block 953002 with 951087
Bug #953002 [src:corsix-th] corsix-th: FTBFS with libsdl2 2.0.10+dfsg1-2
953002 was not blocked by any bugs.
953002 was not blocking any bugs.
Added blocking bug(s) of 953002: 951087
> thanks
Stopping processing here.

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

Bug#945442: Possible to backspace past beginning of string, which appears to be identical to having pressed Enter immediately, without any backspace

[Joerg Dorchain]

On Tue, Mar 03, 2020 at 10:57:41AM +0100, Andras Korn wrote:
> I filed https://github.com/neomutt/neomutt/issues/2161.

Thanks for the effort, but:

Duplicate #2002 and there's already pull request for it #2160.
@gahr gahr closed this 6 minutes ago 

Looks like cherry-pikcing that patch and thinking about the default setting.

Bye,

Joerg


signature.asc
Description: PGP signature

Bug#945442: Possible to backspace past beginning of string, which appears to be identical to having pressed Enter immediately, without any backspace

[Andras Korn]

On Mon, Mar 02, 2020 at 01:45:26PM -0500, Marvin Renich wrote:

Hi,

> I don't have a github account, and do not wish to get one for this.
> Will someone (Debian maintainer for neomutt, or someone else interested
> in this bug) please file this with upstream as a separate bug, pointing
> out that the other github issue is not the same as this bug, even though
> some of the same code may be involved.

I filed https://github.com/neomutt/neomutt/issues/2161.

Best regards,

András

-- 
Microsoft follows standards the same way fish follow migrating caribou.

Processed: Re: Bug#952190: gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #952190 [src:gemma] gemma: FTBFS: dh_auto_test: error: make -j1 check 
returned exit code 2
Added tag(s) upstream.
> forwarded -1 https://github.com/genetics-statistics/GEMMA/issues/216
Bug #952190 [src:gemma] gemma: FTBFS: dh_auto_test: error: make -j1 check 
returned exit code 2
Set Bug forwarded-to-address to 
'https://github.com/genetics-statistics/GEMMA/issues/216'.

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

Bug#952190: gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/genetics-statistics/GEMMA/issues/216

Bug#953016: fife: FTBFS after avoiding #951962: swig4.0: Deprecated command line option: -nosafecstrings. This option is no longer supported.

[Simon McVittie]

Source: fife
Version: 0.4.2-1
Severity: serious
Tags: ftbfs bullseye sid upstream
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://github.com/fifengine/fifengine/issues/1074

I tried compiling fife against a libsdl2 with the patch proposed at

to avoid #951962, and got a different build error:

> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [  1%] Swig compile /<>/obj-x86_64-linux-gnu/fifechan.i for 
> python
> /usr/bin/cmake -E make_directory /<>/obj-x86_64-linux-gnu 
> /<>/obj-x86_64-linux-gnu/CMakeFiles/_fifechan.dir
> [  2%] Swig compile /<>/obj-x86_64-linux-gnu/fife.i for python
> /usr/bin/cmake -E make_directory /<>/obj-x86_64-linux-gnu 
> /<>/obj-x86_64-linux-gnu/CMakeFiles/_fife.dir
> /usr/bin/cmake -E touch 
> /<>/obj-x86_64-linux-gnu/CMakeFiles/_fife.dir/fifePYTHON.stamp
> /usr/bin/cmake -E touch 
> /<>/obj-x86_64-linux-gnu/CMakeFiles/_fifechan.dir/fifechanPYTHON.stamp
> /usr/bin/cmake -E env SWIG_LIB=/usr/share/swig4.0 /usr/bin/swig4.0 -python 
> -modern -fastdispatch -dirvtable -nosafecstrings -noproxydel -fastproxy 
> -fastinit -fastunpack -fastquery -modernargs -nobuildnone -keyword -w511 
> -w473 -w404 -w314 -outdir /<>/obj-x86_64-linux-gnu -c++ 
> -interface _fife -I/<>/obj-x86_64-linux-gnu 
> -I/<>/engine/core -I/<> -I/usr/include 
> -I/usr/include/SDL2 -I/usr/include/AL -I/usr/include/python3.8 -o 
> /<>/obj-x86_64-linux-gnu/CMakeFiles/_fife.dir/fifePYTHON_wrap.cxx
>  /<>/obj-x86_64-linux-gnu/fife.i
> /usr/bin/cmake -E env SWIG_LIB=/usr/share/swig4.0 /usr/bin/swig4.0 -python 
> -modern -fastdispatch -dirvtable -nosafecstrings -noproxydel -fastproxy 
> -fastinit -fastunpack -fastquery -modernargs -nobuildnone -keyword -w511 
> -w473 -w404 -w314 -outdir /<>/obj-x86_64-linux-gnu -c++ 
> -interface _fifechan -I/<>/obj-x86_64-linux-gnu 
> -I/<>/engine/core -I/<> -I/usr/include 
> -I/usr/include/SDL2 -I/usr/include/AL -I/usr/include/python3.8 -o 
> /<>/obj-x86_64-linux-gnu/CMakeFiles/_fifechan.dir/fifechanPYTHON_wrap.cxx
>  /<>/obj-x86_64-linux-gnu/fifechan.i
> Deprecated command line option: -modern. This option is now always on.
> Deprecated command line option: -nosafecstrings. This option is no longer 
> supported.
> make[3]: *** [CMakeFiles/fife_swig_compilation.dir/build.make:139: 
> CMakeFiles/_fife.dir/fifePYTHON.stamp] Error 1

>From http://www.swig.org/Release/CHANGES it appears that -nosafecstrings
was always the default anyway, so simply removing the option might be
enough. Upstream has a 'swig' branch that removes this and another
unsupported option
()
but it hasn't been merged or proposed as a pull request; I don't know why.

smcv

Bug#942365: libgtk2-perl: Package uninstallable

[Alex Andreotti]

Source: libgtk2-perl
Version: 2:1.24993-1
Followup-For: Bug #942365

Dear Maintainer,

   * What led up to the situation?

I'm trying to run obmenu-generator (for openbox) that requires libgtk2-perl

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

apt install libgtk2-perl

   * What was the outcome of this action?

libgtk2-perl : Depends: perlapi-5.28.1 but it is not installable
apt search perlapi
Sorting... Done
Full Text Search... Done

   * What outcome did you expect instead?

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

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#952203: marked as done (seqan: 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 Tue, 03 Mar 2020 09:07:25 +
with message-id 
and subject line Bug#952203: fixed in seqan 1.4.2+dfsg-4
has caused the Debian Bug report #952203,
regarding seqan: 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.)


-- 
952203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: seqan
Version: 1.4.2+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: 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: test_demo_align_align
>   Start  2: test_demo_align_compute_alignment_stats
>   Start  3: test_demo_align_gaps_example
>   Start  4: test_demo_align_global_alignment_banded
>  1/95 Test  #1: test_demo_align_align 
> ..   Passed0.03 sec
>   Start  5: test_demo_align_global_alignment_unbanded
>  2/95 Test  #2: test_demo_align_compute_alignment_stats 
>    Passed0.03 sec
>   Start  6: test_demo_align_integrate_align
>  3/95 Test  #4: test_demo_align_global_alignment_banded 
>    Passed0.03 sec
>   Start  7: test_demo_bam_io_bam_stream
>  4/95 Test  #3: test_demo_align_gaps_example 
> ...   Passed0.03 sec
>   Start  8: test_demo_find_finder_index
>  5/95 Test  #5: test_demo_align_global_alignment_unbanded 
> ..   Passed0.03 sec
>   Start  9: test_demo_find_finder_online
>  6/95 Test  #6: test_demo_align_integrate_align 
>    Passed0.03 sec
>   Start 10: test_demo_graph_graph_algo_dijkstra
>  7/95 Test  #7: test_demo_bam_io_bam_stream 
>    Passed0.03 sec
>   Start 11: test_demo_graph_algorithms_all_pairs_shortest_path
>  8/95 Test  #8: test_demo_find_finder_index 
>    Passed0.03 sec
>   Start 12: test_demo_graph_algorithms_bellman_ford_algorithm
>  9/95 Test  #9: test_demo_find_finder_online 
> ...   Passed0.03 sec
>   Start 13: test_demo_graph_algorithms_breadth_first_search
> 10/95 Test #10: test_demo_graph_graph_algo_dijkstra 
>    Passed0.03 sec
>   Start 14: test_demo_graph_algorithms_dag_shortest_path
> 11/95 Test #11: test_demo_graph_algorithms_all_pairs_shortest_path 
> .   Passed0.03 sec
>   Start 15: test_demo_graph_algorithms_depth_first_search
> 12/95 Test #12: test_demo_graph_algorithms_bellman_ford_algorithm 
> ..   Passed0.03 sec
>   Start 16: test_demo_graph_algorithms_dijkstra
> 13/95 Test #13: test_demo_graph_algorithms_breadth_first_search 
>    Passed0.03 sec
>   Start 17: test_demo_graph_algorithms_floyd_warshall_algorithm
> 14/95 Test #14: test_demo_graph_algorithms_dag_shortest_path 
> ...   Passed0.03 sec
>   Start 18: test_demo_graph_algorithms_ford_fulkerson_algorithm
> 15/95 Test #15: test_demo_graph_algorithms_depth_first_search 
> ..   Passed0.03 sec
>   Start 19: test_demo_graph_algorithms_kruskals_algorithm
> 16/95 Test #16: test_demo_graph_algorithms_dijkstra 
>    Passed0.03 sec
>   Start 20: test_demo_graph_algorithms_prims_algorithm
> 17/95 Test #17: test_demo_graph_algorithms_floyd_warshall_algorithm 
>    Passed0.03 sec
>   Start 21: test_demo_graph_algorithms_strongly_connected_components
> 18/95 Test #18: test_demo_graph_algorithms_ford_fulkerson_algorithm 
>    Passed0.03 sec
>   Start 22: test_demo_graph_algorithms_topological_sort
> 19/95 Test #19: test_demo_graph_algorithms_kruskals_algorithm 
> ..   Passed0.03 sec
>   Start 23: test_demo_graph_algorithms_transitive_closure
> 20/95 Test #20: test_demo_graph_algorithms_prims_algorithm 
> .   Passed0.03 sec
>   Start 24: test_demo_index_index_begin_atEnd_representative
> 21/95 Test #21: 

Bug#938217: marked as done (python-tidylib: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 03 Mar 2020 09:05:56 +
with message-id 
and subject line Bug#938217: fixed in python-tidylib 0.3.2~dfsg-6
has caused the Debian Bug report #938217,
regarding python-tidylib: 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.)


-- 
938217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-tidylib
Version: 0.3.2~dfsg-5
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-tidylib

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-tidylib
Source-Version: 0.3.2~dfsg-6
Done: Dmitry Shachnev 

We believe that the bug you reported is fixed in the latest version of
python-tidylib, 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.
Dmitry Shachnev  (supplier of updated python-tidylib 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 03 Mar 2020 10:54:39 +0300
Source: python-tidylib
Architecture: source
Version: 0.3.2~dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Dmitry Shachnev 
Closes: 938217
Changes:
 python-tidylib (0.3.2~dfsg-6) unstable; urgency=medium
 .
   [ Emmanuel Arias ]
   * d/control: Bump Standards-Version to 4.5.0.
   * Remove Python 2 support (Closes: #938217).
   * d/salsa-ci.yml: enable salsa-ci.
 .
   [ Dmitry Shachnev ]
   * Also drop the Python 2 autopkgtest.
   * Make the Python 3 autopkgtest depend on python3-all.
Checksums-Sha1:
 997ccf45ab830c7769e1a122ca43bc94773ab4ec 2315 python-tidylib_0.3.2~dfsg-6.dsc
 86910e384a5259589c44a5a7a770b5a3cdbd1d84 4584 
python-tidylib_0.3.2~dfsg-6.debian.tar.xz
 8e57995f94cbb46377f02545e5f97303ba572401 9838 
python-tidylib_0.3.2~dfsg-6_source.buildinfo
Checksums-Sha256:
 

Bug#952747: marked as done (libbio-alignio-stockholm-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3))

[Debian Bug Tracking System]

Your message dated Tue, 03 Mar 2020 09:04:47 +
with message-id 
and subject line Bug#952747: fixed in libbio-alignio-stockholm-perl 1.7.3-2
has caused the Debian Bug report #952747,
regarding libbio-alignio-stockholm-perl: missing Breaks+Replaces: 
libbio-perl-perl (<< 1.7.3)
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.)


-- 
952747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbio-alignio-stockholm-perl
Version: 1.7.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../libbio-alignio-stockholm-perl_1.7.3-1_all.deb ...
  Unpacking libbio-alignio-stockholm-perl (1.7.3-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libbio-alignio-stockholm-perl_1.7.3-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/man/man3/Bio::AlignIO::stockholm.3pm.gz', 
which is also in package libbio-perl-perl 1.7.2-3
  Errors were encountered while processing:
   /var/cache/apt/archives/libbio-alignio-stockholm-perl_1.7.3-1_all.deb

IIRC, libbio-perl-perl 1.7.3 was the version that got split up.


cheers,

Andreas


libbio-perl-perl=1.7.2-3_libbio-alignio-stockholm-perl=1.7.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libbio-alignio-stockholm-perl
Source-Version: 1.7.3-2
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
libbio-alignio-stockholm-perl, which is due to be installed in the Debian FTP 
archive.

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated 
libbio-alignio-stockholm-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 03 Mar 2020 09:00:01 +0100
Source: libbio-alignio-stockholm-perl
Architecture: source
Version: 1.7.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 952747
Changes:
 libbio-alignio-stockholm-perl (1.7.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Add missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3)
 Closes: #952747
   * Add salsa-ci file (routine-update)
Checksums-Sha1:
 a27917f85df20702c8be3e4e2453bb16137ab0d5 2284 
libbio-alignio-stockholm-perl_1.7.3-2.dsc
 9b80b333ca155afb28773df1dab39eec5da38f0d 1780 
libbio-alignio-stockholm-perl_1.7.3-2.debian.tar.xz
 998a51da38c5bc7d6a3e06dd0f1cceeafa5dd056 6172 
libbio-alignio-stockholm-perl_1.7.3-2_amd64.buildinfo
Checksums-Sha256:
 22c131b9c3aad31b102e1628225191f37e23f1aef734ea45e495aa946a63078a 2284 
libbio-alignio-stockholm-perl_1.7.3-2.dsc
 f6f3683dc8b27bda0ecfe5cd4ce65bc01911798ed54e29a167fa7928d43cafe8 1780 
libbio-alignio-stockholm-perl_1.7.3-2.debian.tar.xz
 74074186da1f94020ce015ca8286b7a8348c63f957caf1517083369926d41e83 6172 
libbio-alignio-stockholm-perl_1.7.3-2_amd64.buildinfo
Files:
 778d179ea09e14a5de772dc9b5fe3e17 2284 perl optional 
libbio-alignio-stockholm-perl_1.7.3-2.dsc
 6b5bada7af9da7f04f9c73591dcef594 1780 perl optional 
libbio-alignio-stockholm-perl_1.7.3-2.debian.tar.xz
 2cd532bfc7bb7d777d55bedaf6934f05 6172 perl optional 
libbio-alignio-stockholm-perl_1.7.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl5eD08RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGROw/8DVR+WYJ1l4B8CpCFueXYeh7m/aNpoE2N
I2Otl35IYjzv6cfmwCSotbIUg0QBOGuqihfVnkqQ5IeUe3UVRCk4Xds74XvJH4Mi
YZ5+/PIA14tZXoBAtZPzHAPS1eVndbfEMMU6YUiGgDaRcWBNa6W03wOfJOHUofl/

Bug#951962: fife: FTBFS: Could NOT find SDL2 (missing: SDL2_INCLUDE_DIR)

[Simon McVittie]

On Sun, 23 Feb 2020 at 08:26:20 +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

CMake Error at 
/usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message):
  Could NOT find SDL2 (missing: SDL2_INCLUDE_DIR)
Call Stack (most recent call first):
  /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 
(_FPHSA_FAILURE_MESSAGE)
  cmake/FindSDL2.cmake:167 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  CMakeLists.txt:751 (find_package)

I think this is a bug in SDL (#951087, proposed patch:
).

fife might be able to work around it by relying on SDL >= 2.0.4
providing its own CMake integration (which presumably wasn't available when
fife's build system was written), similar to
.

smcv

Processed: affects 951087

[Debian Bug Tracking System]

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

> affects 951087 + src:fife
Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail 
to find SDL2
Added indication that 951087 affects src:fife
> thanks
Stopping processing here.

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

Processed: affects 951087

[Debian Bug Tracking System]

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

> affects 951087 + src:s3d
Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail 
to find SDL2
Added indication that 951087 affects src:s3d
> thanks
Stopping processing here.

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

Processed: affects 951087

[Debian Bug Tracking System]

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

> affects 951087 + src:colobot
Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail 
to find SDL2
Added indication that 951087 affects src:colobot
> thanks
Stopping processing here.

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

Processed: affects 951087

[Debian Bug Tracking System]

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

> affects 951087 + src:spring
Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail 
to find SDL2
Added indication that 951087 affects src:spring
> thanks
Stopping processing here.

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

Processed: affects 951087

[Debian Bug Tracking System]

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

> affects 951087 + src:planetblupi
Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail 
to find SDL2
Added indication that 951087 affects src:planetblupi
> thanks
Stopping processing here.

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

Processed: affects 951087

[Debian Bug Tracking System]

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

> affects 951087 + src:blockattack
Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail 
to find SDL2
Added indication that 951087 affects src:blockattack
> thanks
Stopping processing here.

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

Processed: affects 951087

[Debian Bug Tracking System]

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

> affects 951087 + src:corsix-th
Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail 
to find SDL2
Added indication that 951087 affects src:corsix-th
> thanks
Stopping processing here.

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

Processed: affects 951087

[Debian Bug Tracking System]

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

> affects 951087 + src:trigger-rally
Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail 
to find SDL2
Added indication that 951087 affects src:trigger-rally
> thanks
Stopping processing here.

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

Processed: affects 951087

[Debian Bug Tracking System]

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

> affects 951087 + src:jag
Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail 
to find SDL2
Added indication that 951087 affects src:jag
> thanks
Stopping processing here.

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

Processed: affects 951087

[Debian Bug Tracking System]

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

> affects 951087 + src:pekka-kana-2
Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail 
to find SDL2
Added indication that 951087 affects src:pekka-kana-2
> thanks
Stopping processing here.

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

Processed: affects 951087

[Debian Bug Tracking System]

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

> affects 951087 + src:megaglest
Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail 
to find SDL2
Added indication that 951087 affects src:megaglest
> thanks
Stopping processing here.

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

Processed: affects 951087

[Debian Bug Tracking System]

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

> affects 951087 + src:rbdoom3bfg
Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail 
to find SDL2
Added indication that 951087 affects src:rbdoom3bfg
> thanks
Stopping processing here.

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

Processed: affects 951087

[Debian Bug Tracking System]

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

> affects 951087 + src:mrboom
Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail 
to find SDL2
Added indication that 951087 affects src:mrboom
> thanks
Stopping processing here.

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

Bug#953010: glade: Upgrade to 3.22.2 ( to work with libglib2 >= 2.63.2 )

[Simon McVittie]

Control: tags -1 + upstream patch fixed-upstream
Control: forwarded -1 https://gitlab.gnome.org/GNOME/glade/issues/407

On Tue, 03 Mar 2020 at 11:34:29 +0530, crvi wrote:
> caused by glib >= 2.63.2

https://gitlab.gnome.org/GNOME/glade/commit/a5c583ec483b19b8bb332e4ad24eb57bf11db1f2
appears to be the key commit.

Caused by canonicalization of the property name being enforced in
https://gitlab.gnome.org/GNOME/glib/-/commit/30e630c9df792cf36cdb1cceb3daefbde1dc898a
to improve property and signal performance.

>From codesearch.debian.net, similar fixes might be needed in:

- caja (libcaja-extension/caja-column.c)
- genius (gtkextra/gtkplot.c)
- gnu-smalltalk (packages/gtk/placer.c)
- goocanvas (src/goocanvasrect.c)
- gst-plugins-bad (ext/opencv/gsthanddetect.cpp ROI_X, ROI_Y)
- gutenprint (src/gutenprintui2/curve.c)
- libgnomecanvas (libgnomecanvas/gnome-canvas-line.c)
- nautilus (libnautilus-extension/nautilus-column.c)
- nemo (libnemo-extension/nemo-column.c)

smcv

Processed: Re: Bug#953010: glade: Upgrade to 3.22.2 ( to work with libglib2 >= 2.63.2 )

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + upstream patch fixed-upstream
Bug #953010 [glade] glade: Upgrade to 3.22.2  ( to work with libglib2 >= 2.63.2 
)
Added tag(s) fixed-upstream, upstream, and patch.
> forwarded -1 https://gitlab.gnome.org/GNOME/glade/issues/407
Bug #953010 [glade] glade: Upgrade to 3.22.2  ( to work with libglib2 >= 2.63.2 
)
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/glade/issues/407'.

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

Bug#951087: Bug#953002: corsix-th: FTBFS with libsdl2 2.0.10+dfsg1-2

[Simon McVittie]

On Mon, 02 Mar 2020 at 22:20:28 +0100, Andreas Beckmann wrote:
> libsdl2 2.0.10+dfsg1-2 changed the installation layout and that broke
> SDL detection in corsix-th:
> 
> -- Could NOT find SDL (missing: SDL_INCLUDE_DIR)
> CMake Error at CorsixTH/CMakeLists.txt:110 (message):
>   Error: SDL library not found, it is required to build.  Make sure the path
>   is correctly defined or set the environment variable SDLDIR to the correct
>   location

I think this is a bug in SDL (#951087, proposed patch:
).

corsix-th might be able to work around it by relying on SDL >= 2.0.4
providing its own CMake integration (which presumably wasn't available when
corsix-th's build system was written), similar to
.

smcv