Bug#966960: marked as done (flask-testing: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 09:18:45 +
with message-id 
and subject line Bug#966960: fixed in flask-testing 0.8.0-1
has caused the Debian Bug report #966960,
regarding flask-testing: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p 3.8 returned exit code 13
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.)


-- 
966960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flask-testing
Version: 0.7.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.8_flask-testing/build/flask_testing
> copying flask_testing/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_flask-testing/build/flask_testing
> copying flask_testing/twill.py -> 
> /<>/.pybuild/cpython3_3.8_flask-testing/build/flask_testing
> copying flask_testing/utils.py -> 
> /<>/.pybuild/cpython3_3.8_flask-testing/build/flask_testing
> cd docs && \
> PYTHONPATH=/<> http_proxy= https_proxy= \
> python3 -m sphinx -N -E -T -b html . /<>/.pybuild/docs/html/
> Running Sphinx v2.4.3
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 1 source files that are out of date
> updating environment: [new config] 1 added, 0 changed, 0 removed
> reading sources... [100%] index
> 
> /<>/docs/index.rst:355: WARNING: duplicate object description of 
> flask_testing, other instance in index, use :noindex: for one of them
> /<>/docs/index.rst:2: WARNING: Duplicate ID: 
> "module-flask_testing".
> WARNING: autodoc: failed to import class 'TestCase' from module 
> 'flask_testing'; the following exception was raised:
> cannot import name 'cached_property' from 'werkzeug' 
> (/usr/lib/python3/dist-packages/werkzeug/__init__.py)
> WARNING: autodoc: failed to import class 'Twill' from module 'flask_testing'; 
> the following exception was raised:
> cannot import name 'cached_property' from 'werkzeug' 
> (/usr/lib/python3/dist-packages/werkzeug/__init__.py)
> WARNING: autodoc: failed to import class 'TwillTestCase' from module 
> 'flask_testing'; the following exception was raised:
> cannot import name 'cached_property' from 'werkzeug' 
> (/usr/lib/python3/dist-packages/werkzeug/__init__.py)
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [100%] index
> 
> generating indices...  genindex py-modindexdone
> writing additional pages...  searchdone
> copying static files... ... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 5 warnings.
> 
> The HTML pages are in ../.pybuild/docs/html.
> rm -rf /<>/.pybuild/docs/html/.doctrees
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py test 
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> writing Flask_Testing.egg-info/PKG-INFO
> writing dependency_links to Flask_Testing.egg-info/dependency_links.txt
> writing requirements to Flask_Testing.egg-info/requires.txt
> writing top-level names to Flask_Testing.egg-info/top_level.txt
> reading manifest file 'Flask_Testing.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*.pyc' found under directory 
> 'tests'
> warning: no previously-included files matching '*.pyc' found under directory 
> 'tests'
> warning: no previously-included files matching '*.pyo' found under directory 
> 'docs'
> no previously-included directories found matching 'docs/_build'
> no previously-included directories found matching 'docs/_themes/.git'
> writing manifest file 'Flask_Testing.egg-info/SOURCES.txt'
> running build_ext
> tests (unittest.loader._FailedTest) ... ERROR
> 
> ==
> ERROR: tests (unittest.loader._FailedTest)
> --
> ImportError: Failed to import 

Bug#967157: marked as done (libglade2: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 08:36:27 +
with message-id 
and subject line Bug#967157: fixed in libglade2 1:2.6.4-2.2
has caused the Debian Bug report #967157,
regarding libglade2: Unversioned Python 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.)


-- 
967157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libglade2
Version: 1:2.6.4-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: libglade2
Source-Version: 1:2.6.4-2.2
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
libglade2, 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 967...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libglade2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Aug 2020 10:16:13 +0200
Source: libglade2
Architecture: source
Version: 1:2.6.4-2.2
Distribution: unstable
Urgency: medium
Maintainer: Andreas Rottmann 
Changed-By: Matthias Klose 
Closes: 967157
Changes:
 libglade2 (1:2.6.4-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * (Build-)depend on python2. Closes: #967157.
Checksums-Sha1:
 bddd976467c9e4719f06fe73bd42186bfa6e82e8 2196 libglade2_2.6.4-2.2.dsc
 584aa6a01797b4670e9e772e7c12d9477eaa0e18 6556 libglade2_2.6.4-2.2.debian.tar.xz
 1fbbeca18db52fc67a56e4410d021193e47cdb1f 11297 
libglade2_2.6.4-2.2_source.buildinfo
Checksums-Sha256:
 49db78f542d2dfb68a626f2a4cb5bf9914f1ad06e8139e50d0b3adcaf4bfda40 2196 
libglade2_2.6.4-2.2.dsc
 dcb0a6240629182d3f155bb51de049f023e441aca3944751159131718cec1ade 6556 
libglade2_2.6.4-2.2.debian.tar.xz
 34540ba7562db7decc70be80e69ba665345b8e5c53b40ffc74aaece1a3e343ff 11297 
libglade2_2.6.4-2.2_source.buildinfo
Files:
 fdfaf805cedd036a189f41448ebb4563 2196 devel optional libglade2_2.6.4-2.2.dsc
 a1f0e0db6e87156e5b5855127ac20fc8 6556 devel optional 
libglade2_2.6.4-2.2.debian.tar.xz
 0b9bd2d3a8c5b436142722e4e6e6a3b5 11297 devel optional 
libglade2_2.6.4-2.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl8qauwQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9VqOEACoWWyh0UI+sd9MGwGjN7rwMsp+3VmW
QLUJj24LZg3q24GGdI/mZ22DYXPKEIA0MRqsYVoOyNVFryPG4040ydM6T7PJW4AF
iVjvKR2tnSlCuRHDGUuJ6BEnrSNbIB7NyZboKaiykDmBsVCiZsvOfJ4FE+vWC1ka
igWQvVmFqGHXMp+jMqMlgAdtp8TqoYYTS8HgFAE0JcEyIuDhIFa3ywM7uuylagLA
RWFaY40HniUIP5LYU77PiySXnPCyynw43twORaRIWVoytOYxkiiaFbeoil7FKKJA
wonrEr1yGs33QL8ytOU31MfyBbod/aec16E49M17DoS5QpaYoBkakyiGIMjRPfup
e97VTJsuyfG2EvGZ0vP8MFBqLH9BUMcCgDuM6plOs5oQOkGSwWHaOW1u1gEpaLnD
9MJ4q0wt7ykREmDekQ9W9hKR8esf3DK3V26lfTRd9i1tmqcgmur8zGR/FyrpVh8k
w3gxNsO18AnNurtiUEuGKtl85e3LWtKlcwgIEycrQgEfn4hdgq3ag0es9i5Omk36
EiEuxTMNk9ShkKD0YCVJE1AAT3PtPwepO+ZIlAf6oVyUF1IfOPfHwi4/aWIsxbIK
aRqGOiCqE4llWlKyJ/Rw6KtBA6ORaD0PY1tEO6uy2csVrp3wUtKWdsas9vqkv1J1
1kpEOnbpfA==
=N0sI
-END PGP SIGNATURE End Message ---

Processed: tagging 966965

[Debian Bug Tracking System]

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

> tags 966965 + confirmed
Bug #966965 [src:dune-grid-glue] dune-grid-glue: FTBFS: terminate called after 
throwing an instance of 'Dune::Exception'
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#967021: marked as done (mapsforge: FTBFS: Could not resolve :osmosis-core-0.48.1:.)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 08:36:42 +
with message-id 
and subject line Bug#967021: fixed in mapsforge 0.13.0+dfsg.1-5
has caused the Debian Bug report #967021,
regarding mapsforge: FTBFS: Could not resolve :osmosis-core-0.48.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.)


-- 
967021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mapsforge
Version: 0.13.0+dfsg.1-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 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 '/<>'
> # Set version string correctly
> if [ ! -f build.gradle.debsave ]; then \
>   sed -i.debsave 's/master-SNAPSHOT/0.13.0/' build.gradle ;\
> fi
> dh_auto_configure
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=gradle
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian -Ddebian.package=mapsforge -Dfile.encoding=UTF-8 
> --parallel --max-workers=4 jar
> Initialized native services in: /<>/.gradle/native
> Using 4 worker leases.
> Creating new cache for fileHashes, path 
> /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@9bd0fa6
> Creating new cache for resourceHashesCache, path 
> /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, 
> access org.gradle.cache.internal.DefaultCacheAccess@9bd0fa6
> Creating new cache for fileHashes, path 
> /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@52350abb
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access using Lookup on 
> org.gradle.internal.reflect.JavaMethod 
> (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class 
> java.lang.ClassLoader
> WARNING: Please consider reporting this to the maintainers of 
> org.gradle.internal.reflect.JavaMethod
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Starting Build
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using SubsetScriptTransformer.
> Creating new cache for metadata-1.1/results, path 
> /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@6a0f2853
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using BuildScriptTransformer.
> Compiling settings file '/<>/settings.gradle' using 
> SubsetScriptTransformer.
> Compiling settings file '/<>/settings.gradle' using 
> BuildScriptTransformer.
> Settings evaluated using settings file '/<>/settings.gradle'.
>   Settings file found (/<>/settings.gradle), but 
> rootProject.name isn't defined
>   Root project name not defined in settings.gradle, defaulting to 
> 'mapsforge' instead of the name of the root directory 
> 'mapsforge-0.13.0+dfsg.1'
> Projects loaded. Root project using build file 
> '/<>/build.gradle'.
> Included projects: [root project 'mapsforge', project ':mapsforge-core', 
> project ':mapsforge-map', project ':mapsforge-map-awt', project 
> ':mapsforge-map-reader', project ':mapsforge-map-writer', project 
> ':mapsforge-poi', project ':mapsforge-samples-awt', project 
> ':mapsforge-themes']
>   Keep-alive timer started
>   Adding Debian repository to project 'mapsforge'
>   Adding Debian repository to project 'mapsforge-core'
>   Adding Debian repository to project 'mapsforge-map'
>   Adding Debian repository to project 'mapsforge-map-awt'
>   Adding Debian repository to project 'mapsforge-map-reader'
>   Adding Debian repository to project 'mapsforge-map-writer'
>   Adding Debian repository to project 'mapsforge-poi'
>   Adding Debian repository to project 'mapsforge-samples-awt'
>   Adding Debian repository to project 'mapsforge-themes'
> Parallel execution is an incubating feature.
> Evaluating root project 'mapsforge' using build file 
> '/<>/build.gradle'.
> Compiling build file '/<>/build.gradle' using 
> SubsetScriptTransformer.
> Creating new cache for metadata-2.36/module-metadata, path 
> 

Processed: Bug#967152 marked as pending in java-gnome

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #967152 [src:java-gnome] java-gnome: Unversioned Python removal in 
sid/bullseye
Added tag(s) pending.

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

Bug#967152: marked as pending in java-gnome

[Tony Mancill]

Control: tag -1 pending

Hello,

Bug #967152 in java-gnome 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/java-team/java-gnome/-/commit/24fac5d88b09adee036aa0408cd5e8318eb0f272


Build-depend on python3 and update python patch (Closes: #967152)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/967152

Bug#964623: pmdk: FTBFS: test failed

[Adam Borowski]

Control: severity -1 normal

On Thu, Jul 09, 2020 at 01:27:34PM +0200, Lucas Nussbaum wrote:
> Source: pmdk
> Version: 1.8-1
> Severity: serious

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

> > pmem_check_version@@LIBPMEM_1.0
> > pmem_deep_drain@@LIBPMEM_1.0
> > pmem_deep_flush@@LIBPMEM_1.0

The binutils bug (decoration appended twice) is still there, but I've
disabled this test in 1.9-1.  The package then failed to build for an
unrelated reason, 1.9-2 is now ok.

Downgrading thus.


Meow.
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ It's time to migrate your Imaginary Protocol from version 4i to 6i.
⠈⠳⣄

Processed: Re: Bug#964623: pmdk: FTBFS: test failed

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #964623 [src:pmdk] pmdk: FTBFS: test failed
Severity set to 'normal' from 'serious'

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

Bug#967032: fixed in nodejs 12.18.3~dfsg-1

[Jérémy Lal]

Le mer. 5 août 2020 à 09:54, Moritz Mühlenhoff  a écrit :

> On Tue, Aug 04, 2020 at 10:33:37PM +, Debian FTP Masters wrote:
> >* New upstream version 12.18.3~dfsg
> >* B-D python3, python3-distutils
> >  patch configure to use python3 (Closes: #967032)
>
> debian/tests/control still refers to "python":
>
> | Depends: @, ca-certificates, cdbs, python, procps, curl, build-essential
>

Fixed in 12.18.3~dfsg-2

Thanks

Bug#966966: marked as done (adios: FTBFS: Error: Type mismatch between actual argument at (1) and actual argument at (2) (INTEGER(2)/LOGICAL(8)).)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 07:48:26 +
with message-id 
and subject line Bug#966966: fixed in adios 1.13.1-23
has caused the Debian Bug report #966966,
regarding adios: FTBFS: Error: Type mismatch between actual argument at (1) and 
actual argument at (2) (INTEGER(2)/LOGICAL(8)).
to be marked as done.

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

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


-- 
966966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: adios
Version: 1.13.1-22
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> ar cru libadios.a core/libadios_a-adios.o core/libadios_a-common_adios.o 
> core/libadios_a-adios_internals.o core/libadios_a-adios_internals_mxml.o  
> query/libadios_a-common_query.o query/libadios_a-common_query_read.o 
> query/libadios_a-adios_query_hooks.o query/libadios_a-query_utils.o 
> query/libadios_a-query_minmax.oquery/libadios_a-adios_query.o 
> core/libadios_a-bp_utils.o core/libadios_a-adios_read.o 
> core/libadios_a-adios_read_v1.o core/libadios_a-common_read.o 
> core/libadios_a-adios_read_ext.o core/libadios_a-adios_timing.o 
> core/libadios_a-adios_read_hooks.o core/libadios_a-adios_transport_hooks.o 
> core/libadios_a-util_mpi.o read/libadios_a-read_bp.o 
> read/libadios_a-read_bp_staged.o read/libadios_a-read_bp_staged1.o 
> write/libadios_a-adios_posix.o 
> transforms/libadios_a-adios_transform_sz_write.o 
> transforms/libadios_a-adios_transform_mgard_write.o 
> transforms/libadios_a-adios_transform_sz_read.o 
> transforms/libadios_a-adios_transform_mgard_read.o 
> write/libadios_a-adios_mpi.o write/libadios_a-adios_mpi_lustre.o 
> write/libadios_a-adios_mpi_amr.o write/libadios_a-adios_var_merge.o
> write/libadios_a-adios_phdf5.o write/libadios_a-adios_nc4.o 
> core/libcoreonce_a-a2sel.o core/libcoreonce_a-adios_bp_v1.o 
> core/libcoreonce_a-adios_clock.o core/libcoreonce_a-adios_endianness.o 
> core/libcoreonce_a-adios_error.o core/libcoreonce_a-adios_infocache.o 
> core/libcoreonce_a-adios_logger.o core/libcoreonce_a-adios_socket.o 
> core/libcoreonce_a-buffer.o core/libcoreonce_a-futils.o 
> core/libcoreonce_a-globals.o core/libcoreonce_a-qhashtbl.o 
> core/libcoreonce_a-strutil.o core/libcoreonce_a-util.o 
> core/libcoreonce_a-adios_transform_methods.o 
> core/libcoreonce_a-adiost_callback_internal.o 
> core/libcoreonce_a-adiost_default_tool.o  
> core/transforms/libcoreonce_a-adios_transforms_common.o 
> core/transforms/libcoreonce_a-adios_transforms_hooks.o 
> core/libcoreonce_a-adios_copyspec.o core/libcoreonce_a-adios_subvolume.o  
> core/transforms/libcoreonce_a-adios_transforms_write.o 
> core/transforms/libcoreonce_a-adios_transforms_hooks_write.o 
> core/transforms/libcoreonce_a-adios_transforms_util.o 
> core/transforms/libcoreonce_a-adios_transforms_specparse.o 
> transforms/libcoreonce_a-adios_transform_identity_write.o 
> transforms/libcoreonce_a-adios_transform_zlib_write.o 
> transforms/libcoreonce_a-adios_transform_bzip2_write.o 
> transforms/libcoreonce_a-adios_transform_szip_write.o 
> transforms/libcoreonce_a-adios_transform_isobar_write.o 
> transforms/libcoreonce_a-adios_transform_aplod_write.o 
> transforms/libcoreonce_a-adios_transform_alacrity_write.o 
> transforms/libcoreonce_a-adios_transform_zfp_write.o 
> transforms/libcoreonce_a-adios_transform_lz4_write.o 
> transforms/libcoreonce_a-adios_transform_blosc_write.o  
> core/transforms/libcoreonce_a-adios_transforms_read.o 
> core/transforms/libcoreonce_a-adios_transforms_hooks_read.o 
> core/transforms/libcoreonce_a-adios_transforms_reqgroup.o 
> core/transforms/libcoreonce_a-adios_transforms_datablock.o 
> core/transforms/libcoreonce_a-adios_patchdata.o 
> core/libcoreonce_a-adios_selection_util.o 
> transforms/libcoreonce_a-adios_transform_identity_read.o 
> transforms/libcoreonce_a-adios_transform_zlib_read.o 
> transforms/libcoreonce_a-adios_transform_bzip2_read.o 
> transforms/libcoreonce_a-adios_transform_szip_read.o 
> transforms/libcoreonce_a-adios_transform_isobar_read.o 
> transforms/libcoreonce_a-adios_transform_aplod_read.o 
> transforms/libcoreonce_a-adios_transform_alacrity_read.o 
> transforms/libcoreonce_a-adios_transform_zfp_read.o 
> transforms/libcoreonce_a-adios_transform_lz4_read.o 
> transforms/libcoreonce_a-adios_transform_blosc_read.o 
> mxml/mxml-2.9/libmxml_a-mxml-attr.o mxml/mxml-2.9/libmxml_a-mxml-get.o 
> 

Bug#966723: marked as done (bup: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 07:48:33 +
with message-id 
and subject line Bug#966723: fixed in bup 0.31~git20200728-1
has caused the Debian Bug report #966723,
regarding bup: Unversioned Python 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.)


-- 
966723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bup
Version: 0.29.3-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: bup
Source-Version: 0.31~git20200728-1
Done: Robert Edmonds 

We believe that the bug you reported is fixed in the latest version of
bup, 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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Robert Edmonds  (supplier of updated bup package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Aug 2020 02:39:00 -0400
Source: bup
Architecture: source
Version: 0.31~git20200728-1
Distribution: experimental
Urgency: medium
Maintainer: Robert Edmonds 
Changed-By: Robert Edmonds 
Closes: 936251 966723
Changes:
 bup (0.31~git20200728-1) experimental; urgency=medium
 .
   * New upstream git snapshot due to call for testing
   * debian/: Remove debian/gen_version_py.sh due to upstream changes
   * debian/: Update dependencies and build rules for python3
 (Closes: #936251, #966723)
   * debian/control: Add additional build dependencies acl, libacl1-dev,
 libreadline-dev
   * debian/: Generate lib/bup/source_info.py
   * dev/install-python-script: Use Python 3
Checksums-Sha1:
 2cffcb08344c9a97efd06a75a44870272e90672e 2011 bup_0.31~git20200728-1.dsc
 8daa40fe36c884f50f9583e858e5541dac11518c 452979 
bup_0.31~git20200728.orig.tar.gz
 8ba5cce23f2b5fef41d5a15c4b8ac81d7b207633 6188 
bup_0.31~git20200728-1.debian.tar.xz
 429db937ed1689857f7782607acf9f820e4465ee 7694 
bup_0.31~git20200728-1_amd64.buildinfo
Checksums-Sha256:
 fa7098de95a2d975cf8a1b8b93eb5c8a86cac229b6d91adf04acc147c695eb80 2011 
bup_0.31~git20200728-1.dsc
 d5298fdaaf1975bf482f984bb23872b7c6634b7543ff80b05c8f58cd8279f563 452979 
bup_0.31~git20200728.orig.tar.gz
 c31d796d77a72d0bcc5066a361daee405ba59d469aa938b162300ddbdd352842 6188 
bup_0.31~git20200728-1.debian.tar.xz
 0e700f6de6c0a46d9484c7ce2569568a8a820678b06e65cf205607704a3190f7 7694 
bup_0.31~git20200728-1_amd64.buildinfo
Files:
 9c1c1f7be1aaceb42cf45e1a278a6e81 2011 admin optional bup_0.31~git20200728-1.dsc
 5e9d7dfd2b12149cdf7cdc838665c218 452979 admin optional 
bup_0.31~git20200728.orig.tar.gz
 8792ea6b87d7b58d720fcbe1ba4f4a7b 6188 admin optional 
bup_0.31~git20200728-1.debian.tar.xz
 4e0c137fe2e117e4df7a0f968e55bcf1 7694 admin optional 
bup_0.31~git20200728-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE3z2W7rOCeCDzAmZcAYF6sKr2za4FAl8qXy8ACgkQAYF6sKr2
za5Qgg/8CDyA6Hsv374L7bFN6OljcEz+6f37VqVOSctH9/IJCMwQpVN3NNGsN+s6
/tcQT515Zdp5GKuxtepUet9ccyvMT+t5rc3FP74VjLMzYgDDtrCx43ION3rSrNx/
kcgnfD5RRKb9KcdMyfuDUWbggxGMge9ZvHJydNxqdf9ZmlOU9cOgbcZaKUMcjzZw
VDcpRx0Syy75Li0PWJbpusJR5NtIQecJcpgkAmcNS0LX5SZ6s6KdUqEGckGPq/x2

Bug#946046: marked as done (unison-all should also depend on the old unison version, compatible with Debian 10)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 07:49:42 +
with message-id 
and subject line Bug#946046: fixed in meta-unison 2.48.4+1
has caused the Debian Bug report #946046,
regarding unison-all should also depend on the old unison version, compatible 
with Debian 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.)


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

The purpose of unison-all is the following (see the latest sentence
in particular):

Description: file synchronization tool (all console versions)
 This is a metapackage that depends on all supported console versions
 of Unison, a file synchronization tool.
 .
 Each of the supported versions uses a different protocol version;
 installing this metapackage ensures the ability to synchronize with
 old systems.

But it currently depends only on unison, which is no longer compatible
with Debian 10 (buster), i.e. the current Debian/stable.

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

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

Versions of packages unison-all depends on:
ii  unison  2.48.4-1+b1

unison-all recommends no packages.

unison-all suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: meta-unison
Source-Version: 2.48.4+1
Done: =?utf-8?q?St=C3=A9phane_Glondu?= 

We believe that the bug you reported is fixed in the latest version of
meta-unison, 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 946...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated meta-unison package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Aug 2020 09:28:33 +0200
Source: meta-unison
Architecture: source
Version: 2.48.4+1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 946046
Changes:
 meta-unison (2.48.4+1) unstable; urgency=medium
 .
   * Change packaging structure (Closes: #946046)
 - add new binary packages unison and unison-gtk that depend on
   new unison-2.48 and unison-2.48-gtk and provide symlinks
   * Bump debhelper compat level to 13
   * Bump Standards-Version to 4.5.0
   * Add Rules-Requires-Root: no
Checksums-Sha1:
 44f699f9d33b7fe51902308f887b004f5eaed93c 1463 meta-unison_2.48.4+1.dsc
 f8ac41a074202bd8675a69acf3ba21fd6f98a20c 2144 meta-unison_2.48.4+1.tar.xz
 bb7e937245cb4015278ff522333b90bd8881a6ca 5499 
meta-unison_2.48.4+1_source.buildinfo
Checksums-Sha256:
 02cd302136d53c245d59055aaf943f278ace792a0bb1ede2913c176d5a0a5e94 1463 
meta-unison_2.48.4+1.dsc
 9171a4da9ef798aa4a498ebf1c0c53b850fee9c353ad314e1d6d37a12ad336d5 2144 
meta-unison_2.48.4+1.tar.xz
 937815dc30b5c5a3fd4934c1279d45570ba4235a2684cdf95be6f980fd5a7be5 5499 
meta-unison_2.48.4+1_source.buildinfo
Files:
 1d1b1cea0e9a4661a54e2899fd95f7bf 1463 metapackages optional 
meta-unison_2.48.4+1.dsc
 eaf49914a63dc9cc5bc95a454a649cf8 2144 metapackages optional 
meta-unison_2.48.4+1.tar.xz
 2dca1f319e26e5144f2700bd9f718ca7 5499 metapackages optional 
meta-unison_2.48.4+1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAl8qX+cACgkQIbju8bGJ
MIFMggf8D1ARO5R427CvC5J3xtulhc96sIC/BZDC60Fg+tSbplpLMVYUoTP4RA0d
iUtGU5vXcrn794CubNEsQGlMNl/ftgxtphDfbE4lDaNw/UQWt4FuiCVZuwV0shPb
FaXzYV0pkDsAu2idzsnov78ByxFYwk+sdFIsF3wcJV3cU/eC94koHpfgXf38n7Uc
oHHpMMi01rH8tcQIFT/mf2EoadcgPSsnroz0+IZcNgi6uYl4dBiX2DpiDeo6HXom

Bug#967152: marked as done (java-gnome: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 06:20:13 +
with message-id 
and subject line Bug#967152: fixed in java-gnome 4.1.3-9
has caused the Debian Bug report #967152,
regarding java-gnome: Unversioned Python 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.)


-- 
967152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:java-gnome
Version: 4.1.3-8.1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: java-gnome
Source-Version: 4.1.3-9
Done: tony mancill 

We believe that the bug you reported is fixed in the latest version of
java-gnome, 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 967...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated java-gnome 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, 04 Aug 2020 22:49:34 -0700
Source: java-gnome
Architecture: source
Version: 4.1.3-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 967152
Changes:
 java-gnome (4.1.3-9) unstable; urgency=medium
 .
   * Team upload.
   * Build-depend on python3 and update python patch (Closes: #967152)
Checksums-Sha1:
 97536f518c1b28744918b47c978d3c390d5d2484 2436 java-gnome_4.1.3-9.dsc
 e951623f3ccaaefc2ce6d8ec26853315e8c10c32 10876 java-gnome_4.1.3-9.debian.tar.xz
 261a096ef8e3ebf7711f8ab60dd6b4be769d06b5 16762 
java-gnome_4.1.3-9_amd64.buildinfo
Checksums-Sha256:
 b32f3563cb8116abf6514b9276943020ee3028db0ee52524fa1a37996fb8f67f 2436 
java-gnome_4.1.3-9.dsc
 a1209ab3e4494ef4f7ce85d6c4b298f1451dc9ebb989ed88ba3a930f145c3001 10876 
java-gnome_4.1.3-9.debian.tar.xz
 36578ffb326947b2764bf25ab48d2b1a1dd74c87778c665598187de42201be73 16762 
java-gnome_4.1.3-9_amd64.buildinfo
Files:
 de8fdc7eb408ffab68149a4ddbeb8a89 2436 java optional java-gnome_4.1.3-9.dsc
 fa3c68c1f91b68d5a3ef169cba84f146 10876 java optional 
java-gnome_4.1.3-9.debian.tar.xz
 c0904ac7dd8e6a8595bdde57d6f129fa 16762 java optional 
java-gnome_4.1.3-9_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl8qShQUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpbmhQ//dprIi20h2aFJagysciTqfeVqqUSF
sqIfKsxBr+qMin9vGwLByGjYWGbA/N6PfIvsv7AM9MwBcDs48o0/DI1tqvGQZw5J
UyUFlBM3dmrB/6+WJF3ffWebDDLr+rGmOY0pa73Lbjt1/LootFP1n2SxlpQkZzau
MMVyKxED1kjAJ8BdyCxREorcfkFG26ELKn6wA7q1ozh9OwIpELoU0rg6Gczq5A1y
B0SY1pL7RyBpLAVjI4MvEn3UCYEN6OM0oj5pbfVvM1imWFopzEFWTl+M794Srdpa
qhORaLg/zfJb5SHNvXI5X2YDYnpTReH6pZdYsA0Z6Ev4t82p+Zn1p8+AUMb4GPXf
LECS5FjEOjWT7ppwnzX24cBS48mfDR6VN8X6UreyIRQ2D0IjABvD4HkUncNIji47
SVMMLvc3t9O1hDv5zu09JSYv/1IqUVe2nHfpykfWajl4r2d1k09P7MoP5Z0c4I2/
cTcif+2U7bEX5aVmBs9vZy65zF8CtjFxgdR3prBYnb4Hfoh+1vNQkv2BAIObiPs/
G6wlanIe5A5YyrkD9FrGFDHRDxq+8rHPib1kc5RNQhW+9d8UCrFrv7gxx7ta7/zW
4jcoLztH2GIPw5ozvVhDtWnRodYI7FBHBOGesu/L61eEMXh6+MOWer5z2cR/maO0
QYOi0+R/NMJM06Y=
=Jue0
-END PGP SIGNATURE End Message ---

Bug#964915: marked as done (raspi-firmware: upgrading kernel or firmware causes system to become unbootable on pi 4 (ROOTPART hardcoded to /dev/mmcblk0p2 instead of /dev/mmcblk1p2))

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 06:20:21 +
with message-id 
and subject line Bug#964915: fixed in raspi-firmware 1.20200601-1
has caused the Debian Bug report #964915,
regarding raspi-firmware: upgrading kernel or firmware causes system to become 
unbootable on pi 4 (ROOTPART hardcoded to /dev/mmcblk0p2 instead of 
/dev/mmcblk1p2)
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.)


-- 
964915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: raspi-firmware
Version: 1.20200212-1
Severity: important

On a Raspberry Pi 4B using one of the brand new Pi 4 daily images, I
discovered that installing the firmware-misc-nonfree package would cause
the machine to not boot.

Further investigation found that during the package installation,
/boot/firmware/cmdline.txt was modified in the following manner:

-console=tty0 console=ttyS1,115200 root=LABEL=RASPIROOT rw elevator=deadline 
fsck.repair=yes net.ifnames=0 rootwait
+console=tty0 console=ttyS1,115200 root=/dev/mmcblk0p2 rw elevator=deadline 
fsck.repair=yes net.ifnames=0 rootwait

After I changed this back to LABEL=RASPIROOT, the machine was able to boot
again. On the machine in question, there is no such block device:

dilinger@rpi4-20200710:~$ ls -l /dev/mmcblk0p2
ls: cannot access '/dev/mmcblk0p2': No such file or directory
dilinger@rpi4-20200710:~$ ls -lh /dev/mmcblk1p2 
brw-rw 1 root disk 179, 2 Feb 14  2019 /dev/mmcblk1p2

The culprit here is the following in /etc/kernel/postinst.d/z50-raspi-firmware:

cat >/boot/firmware/cmdline.txt <--- End Message ---
--- Begin Message ---
Source: raspi-firmware
Source-Version: 1.20200601-1
Done: Gunnar Wolf 

We believe that the bug you reported is fixed in the latest version of
raspi-firmware, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gunnar Wolf  (supplier of updated raspi-firmware package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Aug 2020 00:57:15 -0500
Source: raspi-firmware
Architecture: source
Version: 1.20200601-1
Distribution: unstable
Urgency: medium
Maintainer: pkg-raspi 
Changed-By: Gunnar Wolf 
Closes: 964915
Changes:
 raspi-firmware (1.20200601-1) unstable; urgency=medium
 .
   [ Romain Perier ]
   * New upstream version 1.20200601
 .
   [ Gunnar Wolf ]
   * Fix z50-raspi-firmware causing an unbootable system due to the
 hardcoding of partition numbers (Closes: #964915)
Checksums-Sha1:
 b616db017a743cec488fc163860c4a0df1be6165 1640 raspi-firmware_1.20200601-1.dsc
 87c6a745a7ca016687d13523ac2e0c61e6ff3ca5 4862668 
raspi-firmware_1.20200601.orig.tar.xz
 bdd8847fd312fcdbb114b34e82e17f0ab48426a7 25024 
raspi-firmware_1.20200601-1.debian.tar.xz
 0723f4a27687d4c3f0b6362add3746b16ef11b57 5159 
raspi-firmware_1.20200601-1_source.buildinfo
Checksums-Sha256:
 03b88ad1e3a949919153dfdd9bdeb30aa7e796e78b01c952941dc992c67e 1640 
raspi-firmware_1.20200601-1.dsc
 5f34f54122be640a4d0217c4fb5af757f898a17c1ccd9f53f915213dc847e309 4862668 
raspi-firmware_1.20200601.orig.tar.xz
 86476c61904193cb4a683a352e264943f8739c8ccb4ea1c45411ae6ee18f8fd8 25024 
raspi-firmware_1.20200601-1.debian.tar.xz
 f9566630d3123f85fd030cc40276a6d8b44ac086412f732c0c643c99c26bee46 5159 
raspi-firmware_1.20200601-1_source.buildinfo
Files:
 2b7536f42460f44347381e3df3b8e134 1640 non-free/misc optional 
raspi-firmware_1.20200601-1.dsc
 ba79bc985e08203803e392e17ddc42d8 4862668 non-free/misc optional 
raspi-firmware_1.20200601.orig.tar.xz
 759f2ab761aaa0c7e0bb94d048eb16a7 25024 non-free/misc optional 
raspi-firmware_1.20200601-1.debian.tar.xz
 e1542382e6f39e777bd131f1a17fac9f 5159 non-free/misc optional 
raspi-firmware_1.20200601-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iIcEARYIAC8WIQRgswk9lhCOXLlxQu/i9jtDU/RZiQUCXypKgBEcZ3dvbGZAZGVi
aWFuLm9yZwAKCRDi9jtDU/RZiY0XAQC/FNsGxH8Gd/Z41a0G5O9z9UYbyB8wkRiQ
QYCA+I4o/QD8C1izj8jGF3NcATJKkoypcasXX/obthxrwKA+RjJSrwY=
=RW/V
-END PGP SIGNATURE End Message ---

Bug#966787: hardcoded dependency of python-librdf on python

[Sven Joachim]

The python-librdf package has a hardcoded dependency on python.  Simply
removing it should be enough to fix this bug, however the package does
currently FTBFS, see #967932.

Cheers,
   Sven

Bug#967032: fixed in nodejs 12.18.3~dfsg-1

[Moritz Mühlenhoff]

On Tue, Aug 04, 2020 at 10:33:37PM +, Debian FTP Masters wrote:
>* New upstream version 12.18.3~dfsg
>* B-D python3, python3-distutils
>  patch configure to use python3 (Closes: #967032)

debian/tests/control still refers to "python":

| Depends: @, ca-certificates, cdbs, python, procps, curl, build-essential

Cheers,
Moritz

Bug#966865: marked as done (kalign: FTBFS: ld: esl_stopwatch.o:./src/tldevel.h:567: multiple definition of `logsum_lookup'; tldevel.o:./src/tldevel.h:567: first defined here)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 06:48:46 +
with message-id 
and subject line Bug#966865: fixed in kalign 1:3.2.3-4
has caused the Debian Bug report #966865,
regarding kalign: FTBFS: ld: esl_stopwatch.o:./src/tldevel.h:567: multiple 
definition of `logsum_lookup'; tldevel.o:./src/tldevel.h:567: first defined here
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.)


-- 
966865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kalign
Version: 1:3.2.3-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=link gcc -fopenmp -O3 -std=gnu11 
> -DHAVE_AVX2=1 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -mavx2  -D_FORTIFY_SOURCE=2 
> -ffunction-sections -fdata-sections  -Wl,--gc-sections -Wl,--as-needed 
> -Wno-undef -Wl,-z,relro -Wl,-z,now -o timescorealn tldevel.o esl_stopwatch.o 
> time_and_score_aln.o parameters.o alphabet.o rwalign.o misc.o  -lpthread -lm 
> libtool: link: gcc -fopenmp -O3 -std=gnu11 -DHAVE_AVX2=1 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -mavx2 
> -D_FORTIFY_SOURCE=2 -ffunction-sections -fdata-sections -Wl,--gc-sections 
> -Wl,--as-needed -Wno-undef -Wl,-z -Wl,relro -Wl,-z -Wl,now -o timescorealn 
> tldevel.o esl_stopwatch.o time_and_score_aln.o parameters.o alphabet.o 
> rwalign.o misc.o  -lpthread -lm -fopenmp
> /usr/bin/ld: esl_stopwatch.o:./src/tldevel.h:567: multiple definition of 
> `logsum_lookup'; tldevel.o:./src/tldevel.h:567: first defined here
> /usr/bin/ld: time_and_score_aln.o:./src/tldevel.h:567: multiple definition of 
> `logsum_lookup'; tldevel.o:./src/tldevel.h:567: first defined here
> /usr/bin/ld: parameters.o:./src/tldevel.h:567: multiple definition of 
> `logsum_lookup'; tldevel.o:./src/tldevel.h:567: first defined here
> /usr/bin/ld: alphabet.o:./src/tldevel.h:567: multiple definition of 
> `logsum_lookup'; tldevel.o:./src/tldevel.h:567: first defined here
> /usr/bin/ld: rwalign.o:./src/tldevel.h:567: multiple definition of 
> `logsum_lookup'; tldevel.o:./src/tldevel.h:567: first defined here
> /usr/bin/ld: misc.o:./src/tldevel.h:567: multiple definition of 
> `logsum_lookup'; tldevel.o:./src/tldevel.h:567: first defined here
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/kalign_3.2.3-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: kalign
Source-Version: 1:3.2.3-4
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
kalign, 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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated kalign 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, 04 Aug 2020 21:43:28 +
Source: kalign
Architecture: source
Version: 1:3.2.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Nilesh Patra 
Closes: 966865
Changes:
 kalign (1:3.2.3-4) unstable; urgency=medium
 .
   * Team Upload.
   [ Michael R. Crusoe ]
   * patches forwarded upstream
 .
   [ Nilesh Patra ]
   * Fix gcc-10 FTBFS (Closes: #966865)
   * Add manpages
   * compat version: 13, run wrap-and-sort
Checksums-Sha1:
 75e7fe0f2560232c90b94e900e90813f65e0361a 1984 kalign_3.2.3-4.dsc
 43872fbeadc30277c901c97642a6e7c866c5f799 12352 

Bug#967932: redland-bindings: FTBFS: lots of undefined reference errors from ld

[Sven Joachim]

Source: redland-bindings
Version: 1.0.17.1+dfsg-1.3
Severity: serious
Tags: bullseye sid ftbfs

I was looking at #966787, and while the fix for that bug should be easy
(just remove python-librdf's hardcoded python dependency), I could not
build the package in a current amd64 sid chroot:

,
| gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/rasqal -I/usr/include/raptor2  -DSWIG_PYTHON_SILENT_MEMLEAK -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security Redland_wrap.so  -Wl,-z,relro  -lrdf  -lrasqal 
-lraptor2  -o _Redland
| /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/Scrt1.o: in function 
`_start':
| (.text+0x20): undefined reference to `main'
| /usr/bin/ld: Redland_wrap.so: in function `SWIG_Python_ErrorType':
| ./python2.7/./Redland_wrap.c:955: undefined reference to `PyExc_IOError'
| /usr/bin/ld: ./python2.7/./Redland_wrap.c:952: undefined reference to 
`PyExc_MemoryError'
`

In the last successful build[1], the corresponding gcc commandline used
"-shared" and ended with "-o _Redland.so" rather "-o _Redland", so
trying to build an executable is apparently want went wrong here.

A build log is attached for reference.


1. 
https://buildd.debian.org/status/fetch.php?pkg=redland-bindings=amd64=1.0.17.1%2Bdfsg-1.3%2Bb9=1584636898=0



redland-bindings_1.0.17.1+dfsg-1.3_amd64.build.xz
Description: application/xz

Processed: unarchiving 960326

[Debian Bug Tracking System]

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

> unarchive 960326
Bug #960326 {Done: Gianfranco Costamagna } 
[src:json-c] json-c: CVE-2020-12762
Unarchived Bug 960326
> thanks
Stopping processing here.

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

Bug#957020: Fixed already in upstream commit 017e6c6ab95df55f34e339d2139def83e5dada1f

[Alex Murray]

Upstream fixed this via commit
https://github.com/linux-audit/audit-userspace/commit/017e6c6ab95df55f34e339d2139def83e5dada1f
however this has not yet been released in an official release.

Bug#967185: marked as done (openjfx: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 05:48:41 +
with message-id 
and subject line Bug#967185: fixed in openjfx 11.0.7+0-3
has caused the Debian Bug report #967185,
regarding openjfx: Unversioned Python 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.)


-- 
967185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openjfx
Version: 11.0.7+0-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: openjfx
Source-Version: 11.0.7+0-3
Done: tony mancill 

We believe that the bug you reported is fixed in the latest version of
openjfx, 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 967...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated openjfx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Aug 2020 21:47:08 -0700
Source: openjfx
Architecture: source
Version: 11.0.7+0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 937202 967185
Changes:
 openjfx (11.0.7+0-3) unstable; urgency=medium
 .
   * Team upload.
   * Build-depend on python3 (Closes: #937202, #967185)
Checksums-Sha1:
 3aa3a8737eaf5fc0381e4650e395c400026096e8 2764 openjfx_11.0.7+0-3.dsc
 94452cb7b20539af1a2c9faba01b49728b108a1d 16304 openjfx_11.0.7+0-3.debian.tar.xz
 9e2beaf154dda81fe4fd2d9a37c6bb9f4b30d839 24155 
openjfx_11.0.7+0-3_amd64.buildinfo
Checksums-Sha256:
 2b9f38c8d004904b360c9345dff2dacf75f4df690a155a7efdd8a722b5827e07 2764 
openjfx_11.0.7+0-3.dsc
 0e3dc0df15c595b9bde323314f048823a66066e48b464ced41eb51a77bf92b29 16304 
openjfx_11.0.7+0-3.debian.tar.xz
 1e31a23d467968439a2882eaffef7c97066ce23847689670e2e998c1ff68ac43 24155 
openjfx_11.0.7+0-3_amd64.buildinfo
Files:
 c9530de6f5c3157cc579de422c421088 2764 java optional openjfx_11.0.7+0-3.dsc
 b76eac8f86c8a1f56eb3a751bf1e0345 16304 java optional 
openjfx_11.0.7+0-3.debian.tar.xz
 db9199583014134db360d5de3ffcd545 24155 java optional 
openjfx_11.0.7+0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl8rlcMUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpauuRAAkXIoQ586vDQEUrzN1RugDO7zDQtD
vlkt6CCxqfidvcqwT+mDey2kgZsGZ1inmy8HOcNy6cLlMAHdGLC8jQWnp7otLMtr
9yDnKLIKkAbYlFeovXg0RSTE+k/tYiELenLz6ptBkSrpCpYn7uLhOKB8lIN42BKT
r3S3oF0s9FUbOSkkpx9CkSx9Y4Ua7C5QEWAXvK9trzcb1Y1ruJlHRadmHx43hSlZ
VhKa+truh66OdVz6iVQQfBN/ugUo1g6D7ocRSbfV4Qe7+rfh606ARj6S0D2V7QQZ
fxbUnDook1ShC8Ni3zXPl+X3t+cLj5yY8KRrKrB4Wx7nZrmPszQx9vgaqyHF3Pjg
f1aCEgjKBsrgTJSopla6zDdyDsFNeqwXaVaUeQzcotqPAN+SEwnbLIBVi8nb+Gun
y92AhPAI+xUUhmhRcMgKTC6M+YmlzqM0WpTrvMnr/kvF4hDNfPR3T7MuFh2rZWHk
UYnVbvEzBhGuYl56P0ySZGKUvjqkyyyqXgXYiyuxa/17FfMnKS1aOLlDW/WRkgWr
ecdoiPfRWJGkoN4jUhrKrI6OcMSaTiwfXn7YIzPbcW1eZhcCOyUoLGJjPwMEXReV
YVsipbaw5XdScgSvHSMH7uXUHE1Mv5igF3m/aravUskwdTeuuKwcsTKfRsCaD49G
GLm2HAXu7tP9mc0=
=sNEh
-END PGP SIGNATURE End Message ---

Processed (with 1 error): unarchiving 960326, found 960326 in 0.12.1+ds-2, closing 960326

[Debian Bug Tracking System]

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

> unarchive 960326
> found 960326 0.12.1+ds-2
Bug #960326 {Done: Gianfranco Costamagna } 
[src:json-c] json-c: CVE-2020-12762
Marked as found in versions json-c/0.12.1+ds-2.
> close 960326 0.12.1+ds-2+deb10u1
Bug #960326 {Done: Gianfranco Costamagna } 
[src:json-c] json-c: CVE-2020-12762
Marked as fixed in versions json-c/0.12.1+ds-2+deb10u1.
Bug #960326 {Done: Gianfranco Costamagna } 
[src:json-c] json-c: CVE-2020-12762
Bug 960326 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#966914: sambamba: FTBFS: collect2: error: ld returned 1 exit status

[Andreas Tille]

On Thu, Aug 06, 2020 at 03:49:51AM +0200, Matthias Klumpp wrote:
> Where does the
> `bgzf.c` file reference come from?

I used find on my local disk and several projects do contain bgzf.c.
My guess is these are all code copies from htslib - thus I'd assume
it comes from htslib.  This seems quite probable since

   cram/htslib.d

in sambamba contains the string bgzf several times.

Kind regards

   Andreas. 

-- 
http://fam-tille.de

Bug#967204: marked as done (python-mode: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 5 Aug 2020 16:10:09 +0200
with message-id <7527aa13-762a-935a-c223-2f52e428c...@debian.org>
and subject line Re: python-mode: Unversioned Python removal in sid/bullseye
has caused the Debian Bug report #967204,
regarding python-mode: Unversioned Python 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.)


-- 
967204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-mode
Version: 1:6.2.3-1.3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: 1:6.2.3-1.4

Fixed.--- End Message ---

Bug#937927: python-mode: Python2 removal in sid/bullseye

[Matthias Klose]

Control: severity -1 important

Now uses python2 explicitly.

Processed: Re: Bug#964541: flatpak: Wrong argument order for clone syscall seccomp filter on s390x (Was: make: Regression on s390x, echo EPERM, caused by posix_spawn change)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 flatpak
Bug #964541 [make-dfsg] make: Regression on s390x, echo EPERM, caused by 
posix_spawn change
Bug reassigned from package 'make-dfsg' to 'flatpak'.
No longer marked as found in versions 4.3-4.
Ignoring request to alter fixed versions of bug #964541 to the same values 
previously set
> retitle -1 flatpak: Wrong argument order for clone syscall seccomp filter on 
> s390x
Bug #964541 [flatpak] make: Regression on s390x, echo EPERM, caused by 
posix_spawn change
Changed Bug title to 'flatpak: Wrong argument order for clone syscall seccomp 
filter on s390x' from 'make: Regression on s390x, echo EPERM, caused by 
posix_spawn change'.

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

Bug#964541: flatpak: Wrong argument order for clone syscall seccomp filter on s390x (Was: make: Regression on s390x, echo EPERM, caused by posix_spawn change)

[Julian Andres Klode]

Control: reassign -1 flatpak
Control: retitle -1 flatpak: Wrong argument order for clone syscall seccomp 
filter on s390x

Hello flatpak maintainer!

On Wed, Aug 05, 2020 at 03:19:39PM +0200, Christian Borntraeger wrote:
> 
> On 21.07.20 13:24, Julian Andres Klode wrote:
> > On Tue, Jul 21, 2020 at 12:49:59PM +0200, Christian Borntraeger wrote:
> >> On 21.07.20 10:18, Adrian Bunk wrote:
> >>> [ adding debian-s390 to Cc ]
> >>>
> >>> On Wed, Jul 08, 2020 at 01:42:33PM +0200, Julian Andres Klode wrote:
>  Package: make-dfsg
>  Version: 4.3-4
>  Severity: serious
>  Tags: patch
>  User: ubuntu-de...@lists.ubuntu.com
>  Usertags: origin-ubuntu groovy ubuntu-patch
> 
>  In Ubuntu, the attached patch was applied to achieve the following:
> 
>  The autopkgtests for flatpak-builder/s390x where failing with
> 
>    echo Building
>    make: echo: Operation not permitted
>    make: *** [Makefile:2: all] Error 127
> >>
> >> Julian,
> >>
> >> is there a launchpad entry for the Ubuntu bug that was fixed by this 
> >> change?
> > 
> > Yes, https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1886814, it's 
> > also
> > in the IBM bugzilla thingy - you can see Andreas Krebbel is replying to 
> > that.
> 
> FWIW, Stefan Liebler looked into this and this needs to be fixed in 
> flatpak-build.
> See the bug for details. 

flatpak has the wrong argument order in the seccomp filter for 390x, the
attached patch should fix it.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
Description: Fix argument order of clone() for s390x in seccomp filter
 clone() is a mad syscall with about 4 different argument orders. While
 most of them agree that argument 0 is flags, s390 and s390x have the
 flags argument second - A0 is the child stack pointer there.
Author: Julian Andres Klode 

Bug-Debian: https://bugs.debian.org/964541
Bug-Ubuntu: https://launchpad.net/bugs/1886814
Forwarded: no
Last-Update: 2020-08-05

--- flatpak-1.8.1.orig/common/flatpak-run.c
+++ flatpak-1.8.1/common/flatpak-run.c
@@ -2667,7 +2667,11 @@ setup_seccomp (FlatpakBwrap   *bwrap,
 {SCMP_SYS (unshare)},
 {SCMP_SYS (mount)},
 {SCMP_SYS (pivot_root)},
+#if defined(__s390__) || defined(__s390x__)
+{SCMP_SYS (clone), _A1 (SCMP_CMP_MASKED_EQ, CLONE_NEWUSER, CLONE_NEWUSER)},
+#else
 {SCMP_SYS (clone), _A0 (SCMP_CMP_MASKED_EQ, CLONE_NEWUSER, CLONE_NEWUSER)},
+#endif
 
 /* Don't allow faking input to the controlling tty (CVE-2017-5226) */
 {SCMP_SYS (ioctl), _A1 (SCMP_CMP_MASKED_EQ, 0xu, (int) TIOCSTI)},

Processed: Bug fixed, but new version needs work on autopkgtest (Was: Bug#966876: trinityrnaseq: FTBFS: sift_bam_max_cov.cpp:99:10: error: ‘string’ is not a member of ‘std’)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #966876 [src:trinityrnaseq] trinityrnaseq: FTBFS: 
sift_bam_max_cov.cpp:99:10: error: ‘string’ is not a member of ‘std’
Added tag(s) pending.

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

Bug#966876: Bug fixed, but new version needs work on autopkgtest (Was: Bug#966876: trinityrnaseq: FTBFS: sift_bam_max_cov.cpp:99:10: error: ‘string’ is not a member of ‘std’)

[Andreas Tille]

Control: tags -1 pending

On Mon, Aug 03, 2020 at 10:07:38AM +0200, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> > -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> > -Wl,-z,relro -Wl,-z,now sift_bam_max_cov.cpp -Wall -lhts -O2 -o bamsifter
> > sift_bam_max_cov.cpp: In function ‘int main(int, char**)’:
> > sift_bam_max_cov.cpp:99:10: error: ‘string’ is not a member of ‘std’
> >99 | std::string tmp_text(input_header->text, input_header->l_text);
> >   |  ^~
> > sift_bam_max_cov.cpp:16:1: note: ‘std::string’ is defined in header 
> > ‘’; did you forget to ‘#include ’?
> >15 | #include "htslib/bgzf.h"
> >   +++ |+#include 

I've fixed this bug (and I think new upstream has found another way by using
'-std=c++11' option (which would be hopefully unneeded by my patch but I did
not tested). 

Unfortunately the autopkgtest is broken by the new version which I imported
as well.  Not sure whether

   seqtk-trinity is missing and thus autopkgtest fails

is the only problem.  seqtk-trinity was provided as *binary* which needed
to be removed in Files-Excluded.  I have not checked how / whether it is
build and whether other issues might exist.

Any takers for the remaining issues?

Kind regards

   Andreas.

-- 
http://fam-tille.de

Processed: Bug#964679 marked as pending in gtk+3.0

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #964679 [src:gtk+3.0] gtk+3.0: FTBFS: dpkg-gensymbols: error: some new 
symbols appeared in the symbols file: see diff output below
Ignoring request to alter tags of bug #964679 to the same tags previously set

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

Processed: py2removal bugs severity updates - 2020-08-05 14:33:55.682620+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # and https://lists.debian.org/debian-python/2020/03/msg00087.html
> # mail threads for more details on this severity update
> # python-mode is a module and has 0 external rdeps or not in testing
> severity 937927 serious
Bug #937927 [src:python-mode] python-mode: Python2 removal in sid/bullseye
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Bug#957995: xscorch: diff for NMU version 0.2.1-1+nmu4

[Luis Paulo Linares]

Control: tags 957995 + pending

Dear maintainer,

I've prepared an NMU for xscorch (versioned as 0.2.1-1+nmu3) and
uploaded it to mentors to be sponsored. Please feel free to tell me
if I should remove it. A debdiff showing all changes is attatched.

Regards,

-- 
Luis Paulo (lpfll)
diff -Nru xscorch-0.2.1/debian/changelog xscorch-0.2.1/debian/changelog
--- xscorch-0.2.1/debian/changelog  2020-07-02 09:57:17.0 -0300
+++ xscorch-0.2.1/debian/changelog  2020-08-05 01:00:19.0 -0300
@@ -1,3 +1,11 @@
+xscorch (0.2.1-1+nmu4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/gcc10.patch: fix a FTBFS witch gcc 10. Thanks to
+Reiner Herrmann . (Closes: #957995)
+
+ -- Luis Paulo Linares   Wed, 05 Aug 2020 01:00:19 -0300
+
 xscorch (0.2.1-1+nmu3) unstable; urgency=medium

   * Non-maintainer upload.
diff -Nru xscorch-0.2.1/debian/patches/gcc10.patch xscorch-0.2.1/debian/patches/gcc10.patch
--- xscorch-0.2.1/debian/patches/gcc10.patch1969-12-31 21:00:00.0 -0300
+++ xscorch-0.2.1/debian/patches/gcc10.patch2020-08-05 01:00:19.0 -0300
@@ -0,0 +1,29 @@
+Description: Fix FTBFS with GCC 10
+Author: Reiner Herrmann 
+Bug-Debian: https://bugs.debian.org/957995
+Last-Update: 2020-08-05
+Index: xscorch-0.2.1/sgame/slscape.c
+===
+--- xscorch-0.2.1.orig/sgame/slscape.c
 xscorch-0.2.1/sgame/slscape.c
+@@ -56,6 +56,7 @@ static double _sc_lscape_eval_plains(dou
+ static double _sc_lscape_eval_traditional(double x);
+ static double _sc_lscape_eval_valley(double x);
+
++double (*_sc_lscape_eval)(double x);
+
+
+ static double _sc_lscape_eval_none(__libj_unused double x) {
+Index: xscorch-0.2.1/sgame/slscape.h
+===
+--- xscorch-0.2.1.orig/sgame/slscape.h
 xscorch-0.2.1/sgame/slscape.h
+@@ -64,7 +64,7 @@ void sc_lscape_setup(const struct _sc_co
+
+ /* Interface to the profile evaluating function */
+ #define sc_lscape_eval(x)  ((*_sc_lscape_eval)(x))
+-double (*_sc_lscape_eval)(double x);
++extern double (*_sc_lscape_eval)(double x);
+
+
+ #endif /* __slscape_h_included */
diff -Nru xscorch-0.2.1/debian/patches/series xscorch-0.2.1/debian/patches/series
--- xscorch-0.2.1/debian/patches/series 2018-03-31 11:36:36.0 -0300
+++ xscorch-0.2.1/debian/patches/series 2020-08-05 01:00:19.0 -0300
@@ -1,2 +1,3 @@
 overlapping-memcpy
 gdk-include
+gcc10.patch

Processed: xscorch: diff for NMU version 0.2.1-1+nmu4

[Debian Bug Tracking System]

Processing control commands:

> tags 957995 + pending
Bug #957995 [src:xscorch] xscorch: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#964679: marked as pending in gtk+3.0

[Sebastien Bacher]

Control: tag -1 pending

Hello,

Bug #964679 in gtk+3.0 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/gnome-team/gtk3/-/commit/df6191ce8af70e94235b96cc8a513c0a65a51b63


Add proposed patch to fix FTBFS with newer GLib versions

Closes: #964679


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964679

Bug#966910: marked as done (polymake: FTBFS: pool_allocator.h:36:19: error: ‘typedef std::size_t __gnu_cxx::__pool_alloc_base::size_t’ is private within this context)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 13:48:40 +
with message-id 
and subject line Bug#966910: fixed in polymake 4.1-3
has caused the Debian Bug report #966910,
regarding polymake: FTBFS: pool_allocator.h:36:19: error: ‘typedef std::size_t 
__gnu_cxx::__pool_alloc_base::size_t’ is private within this context
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.)


-- 
966910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: polymake
Version: 4.0r1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>   g++ -c -o /<>/build/Opt/apps/common/bounding_box.o -MMD -MT 
> /<>/build/Opt/apps/common/bounding_box.o -MF 
> /<>/build/Opt/apps/common/bounding_box.o.d -fPIC -pipe -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 
> -ftemplate-depth-200 -fno-strict-aliasing -fopenmp -Wshadow -Wlogical-op 
> -Wconversion -Wzero-as-null-pointer-constant -Wno-parentheses 
> -Wno-error=unused-function -Wno-stringop-overflow -DPOLYMAKE_WITH_FLINT  
> -DPOLYMAKE_DEBUG=0 -DNDEBUG -O2 -DPOLYMAKE_APPNAME=common 
> -DPOLYMAKE_DEFINITION_SOURCE_FILE="bounding_box.cc" 
> -DPOLYMAKE_DEFINITION_SOURCE_DIR="../../src" 
> -I/<>/include/app-wrappers -I/<>/include/apps 
> -I/<>/include/external/permlib 
> -I/<>/include/external/TOSimplex 
> -I/<>/include/core-wrappers -I/<>/include/core 
> /<>/apps/common/cpperl/generated/wrap-bounding_box.cc && : 
> 'COMPILER_USED=10.2.0'
> In file included from 
> /<>/include/core/polymake/internal/type_manip.h:21,
>  from 
> /<>/include/core/polymake/internal/iterators.h:21,
>  from 
> /<>/include/core/polymake/internal/shared_object.h:21,
>  from 
> /<>/include/core/polymake/internal/singular_containers.h:21,
>  from 
> /<>/include/core/polymake/internal/modified_containers.h:21,
>  from 
> /<>/include/core/polymake/internal/iterator_filters.h:21,
>  from 
> /<>/include/core/polymake/internal/sparse.h:21,
>  from /<>/include/core/polymake/GenericIO.h:21,
>  from /<>/include/core/polymake/perl/Value.h:21,
>  from /<>/include/core/polymake/client.h:22,
>  from 
> /<>/include/apps/polymake/common/bounding_box.h:21,
>  from 
> /<>/apps/common/cpperl/generated/../../src/bounding_box.cc:18,
>  from 
> /<>/apps/common/cpperl/generated/wrap-bounding_box.cc:6:
> /<>/include/core/polymake/internal/pool_allocator.h:36:19: 
> error: ‘typedef std::size_t __gnu_cxx::__pool_alloc_base::size_t’ is private 
> within this context
>36 |void* allocate(size_t n)
>   |   ^~
> In file included from 
> /<>/include/core/polymake/internal/pool_allocator.h:25,
>  from 
> /<>/include/core/polymake/internal/type_manip.h:21,
>  from 
> /<>/include/core/polymake/internal/iterators.h:21,
>  from 
> /<>/include/core/polymake/internal/shared_object.h:21,
>  from 
> /<>/include/core/polymake/internal/singular_containers.h:21,
>  from 
> /<>/include/core/polymake/internal/modified_containers.h:21,
>  from 
> /<>/include/core/polymake/internal/iterator_filters.h:21,
>  from 
> /<>/include/core/polymake/internal/sparse.h:21,
>  from /<>/include/core/polymake/GenericIO.h:21,
>  from /<>/include/core/polymake/perl/Value.h:21,
>  from /<>/include/core/polymake/client.h:22,
>  from 
> /<>/include/apps/polymake/common/bounding_box.h:21,
>  from 
> /<>/apps/common/cpperl/generated/../../src/bounding_box.cc:18,
>  from 
> /<>/apps/common/cpperl/generated/wrap-bounding_box.cc:6:
> /usr/include/c++/10/ext/pool_allocator.h:77:27: note: declared private here
>77 |   typedef std::size_t size_t;
>   |   ^~
> In file included from 
> /<>/include/core/polymake/internal/type_manip.h:21,
>  from 
> /<>/include/core/polymake/internal/iterators.h:21,
>  from 
> /<>/include/core/polymake/internal/shared_object.h:21,
>  from 
> /<>/include/core/polymake/internal/singular_containers.h:21,
>  from 
> 

Processed: Re: python-mode: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #937927 [src:python-mode] python-mode: Python2 removal in sid/bullseye
Severity set to 'important' from 'serious'

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

Bug#966910: marked as done (polymake: FTBFS: pool_allocator.h:36:19: error: ‘typedef std::size_t __gnu_cxx::__pool_alloc_base::size_t’ is private within this context)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 15:04:13 +
with message-id 
and subject line Bug#966910: fixed in polymake 4.1-4
has caused the Debian Bug report #966910,
regarding polymake: FTBFS: pool_allocator.h:36:19: error: ‘typedef std::size_t 
__gnu_cxx::__pool_alloc_base::size_t’ is private within this context
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.)


-- 
966910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: polymake
Version: 4.0r1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>   g++ -c -o /<>/build/Opt/apps/common/bounding_box.o -MMD -MT 
> /<>/build/Opt/apps/common/bounding_box.o -MF 
> /<>/build/Opt/apps/common/bounding_box.o.d -fPIC -pipe -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 
> -ftemplate-depth-200 -fno-strict-aliasing -fopenmp -Wshadow -Wlogical-op 
> -Wconversion -Wzero-as-null-pointer-constant -Wno-parentheses 
> -Wno-error=unused-function -Wno-stringop-overflow -DPOLYMAKE_WITH_FLINT  
> -DPOLYMAKE_DEBUG=0 -DNDEBUG -O2 -DPOLYMAKE_APPNAME=common 
> -DPOLYMAKE_DEFINITION_SOURCE_FILE="bounding_box.cc" 
> -DPOLYMAKE_DEFINITION_SOURCE_DIR="../../src" 
> -I/<>/include/app-wrappers -I/<>/include/apps 
> -I/<>/include/external/permlib 
> -I/<>/include/external/TOSimplex 
> -I/<>/include/core-wrappers -I/<>/include/core 
> /<>/apps/common/cpperl/generated/wrap-bounding_box.cc && : 
> 'COMPILER_USED=10.2.0'
> In file included from 
> /<>/include/core/polymake/internal/type_manip.h:21,
>  from 
> /<>/include/core/polymake/internal/iterators.h:21,
>  from 
> /<>/include/core/polymake/internal/shared_object.h:21,
>  from 
> /<>/include/core/polymake/internal/singular_containers.h:21,
>  from 
> /<>/include/core/polymake/internal/modified_containers.h:21,
>  from 
> /<>/include/core/polymake/internal/iterator_filters.h:21,
>  from 
> /<>/include/core/polymake/internal/sparse.h:21,
>  from /<>/include/core/polymake/GenericIO.h:21,
>  from /<>/include/core/polymake/perl/Value.h:21,
>  from /<>/include/core/polymake/client.h:22,
>  from 
> /<>/include/apps/polymake/common/bounding_box.h:21,
>  from 
> /<>/apps/common/cpperl/generated/../../src/bounding_box.cc:18,
>  from 
> /<>/apps/common/cpperl/generated/wrap-bounding_box.cc:6:
> /<>/include/core/polymake/internal/pool_allocator.h:36:19: 
> error: ‘typedef std::size_t __gnu_cxx::__pool_alloc_base::size_t’ is private 
> within this context
>36 |void* allocate(size_t n)
>   |   ^~
> In file included from 
> /<>/include/core/polymake/internal/pool_allocator.h:25,
>  from 
> /<>/include/core/polymake/internal/type_manip.h:21,
>  from 
> /<>/include/core/polymake/internal/iterators.h:21,
>  from 
> /<>/include/core/polymake/internal/shared_object.h:21,
>  from 
> /<>/include/core/polymake/internal/singular_containers.h:21,
>  from 
> /<>/include/core/polymake/internal/modified_containers.h:21,
>  from 
> /<>/include/core/polymake/internal/iterator_filters.h:21,
>  from 
> /<>/include/core/polymake/internal/sparse.h:21,
>  from /<>/include/core/polymake/GenericIO.h:21,
>  from /<>/include/core/polymake/perl/Value.h:21,
>  from /<>/include/core/polymake/client.h:22,
>  from 
> /<>/include/apps/polymake/common/bounding_box.h:21,
>  from 
> /<>/apps/common/cpperl/generated/../../src/bounding_box.cc:18,
>  from 
> /<>/apps/common/cpperl/generated/wrap-bounding_box.cc:6:
> /usr/include/c++/10/ext/pool_allocator.h:77:27: note: declared private here
>77 |   typedef std::size_t size_t;
>   |   ^~
> In file included from 
> /<>/include/core/polymake/internal/type_manip.h:21,
>  from 
> /<>/include/core/polymake/internal/iterators.h:21,
>  from 
> /<>/include/core/polymake/internal/shared_object.h:21,
>  from 
> /<>/include/core/polymake/internal/singular_containers.h:21,
>  from 
> 

Bug#967146: marked as done (guile-gnome-platform: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 5 Aug 2020 12:40:52 +0200
with message-id <5a4c1c09-b5fb-0739-8d18-79da2f97f...@debian.org>
and subject line Re: Bug#967146: guile-gnome-platform: Unversioned Python 
removal in sid/bullseye
has caused the Debian Bug report #967146,
regarding guile-gnome-platform: Unversioned Python 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.)


-- 
967146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:guile-gnome-platform
Version: 2.16.5-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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 ---
fixed libglade2 is now in the archive.

On 8/4/20 12:03 PM, Tommi Höynälänmaa wrote:
> Hi
> 
> I checked file debian/control and the test directories. I could not
> find any Python dependencies. Where are they?
> 
>  - Tommi Höynälänmaa
> 
> ti, 2020-08-04 kello 09:28 +, Matthias Klose kirjoitti:
>> Package: src:guile-gnome-platform
>> Version: 2.16.5-2
>> Severity: serious
>> Tags: sid bullseye
>> User: debian-pyt...@lists.debian.org
>> Usertags: py2unversioned
>>
>> 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
>>
>> We will keep some Python2 package as discussed in
>> https://lists.debian.org/debian-python/2020/07/msg00039.html
>> but removing the unversioned python packages python-minimal, python,
>> python-dev, python-dbg, python-doc.
>>
>> Your package either build-depends, depends on one of those packages.
>> Please either convert these packages to Python3, or if that is not
>> possible, replaces the dependencies on the unversioned Python
>> packages with one of the python2 dependencies (python2, python2-dev,
>> python2-dbg, python2-doc).
>>
>> Please check for dependencies, build dependencies AND autopkg tests.
>>
>> 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 ---

Bug#967134: marked as done (g3dviewer: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 5 Aug 2020 12:41:26 +0200
with message-id <8461c094-eeab-c344-16c9-383ac765b...@debian.org>
and subject line Re: Bug#967134: g3dviewer: Unversioned Python removal in 
sid/bullseye
has caused the Debian Bug report #967134,
regarding g3dviewer: Unversioned Python 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.)


-- 
967134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:g3dviewer
Version: 0.2.99.5~svn130-11
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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 ---
On 8/4/20 11:36 AM, Sven Eckelmann wrote:
> tags 967134 + moreinfo
> thanks
> 
> On Tuesday, 4 August 2020 11:27:54 CEST Matthias Klose wrote:
> [...]
>> Your package either build-depends, depends on one of those packages.
>> Please either convert these packages to Python3, or if that is not
>> possible, replaces the dependencies on the unversioned Python
>> packages with one of the python2 dependencies (python2, python2-dev,
>> python2-dbg, python2-doc).
> 
> Hm? Where does it directly depend on python? I would like to fix it 
> but I don't see what.

a fixed libglade2-dev is now in the archive.--- End Message ---

Processed: Re: Bug#966983: python-skbio: FTBFS: dh_sphinxdoc: error: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/search.html does not load searchindex.js

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible
Bug #966983 [src:python-skbio] python-skbio: FTBFS: dh_sphinxdoc: error: 
debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/search.html does 
not load searchindex.js
Added tag(s) unreproducible.

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

Bug#957019: atlc: diff for NMU version 4.6.1-2.1

[Sudip Mukherjee]

Control: tags 957019 + patch
Control: tags 957019 + pending

Dear maintainer,

I've prepared an NMU for atlc (versioned as 4.6.1-2.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -Nru atlc-4.6.1/debian/changelog atlc-4.6.1/debian/changelog
--- atlc-4.6.1/debian/changelog 2017-12-30 04:06:57.0 +
+++ atlc-4.6.1/debian/changelog 2020-08-05 12:17:38.0 +0100
@@ -1,3 +1,10 @@
+atlc (4.6.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957019)
+
+ -- Sudip Mukherjee   Wed, 05 Aug 2020 12:17:38 
+0100
+
 atlc (4.6.1-2) unstable; urgency=medium
 
   * remove libgsl0-dev build dependency, closes: #823876
diff -Nru atlc-4.6.1/debian/patches/fix_ftbfs.patch 
atlc-4.6.1/debian/patches/fix_ftbfs.patch
--- atlc-4.6.1/debian/patches/fix_ftbfs.patch   1970-01-01 01:00:00.0 
+0100
+++ atlc-4.6.1/debian/patches/fix_ftbfs.patch   2020-08-05 12:10:16.0 
+0100
@@ -0,0 +1,19 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/957019
+Forwarded: no
+
+---
+
+--- atlc-4.6.1.orig/src/swap_conductor_voltages.c
 atlc-4.6.1/src/swap_conductor_voltages.c
+@@ -36,7 +36,7 @@ CONDUCTOR_MINUS_ONE_V in definitions.h *
+ #include "definitions.h"
+ 
+ extern int width, height;
+-unsigned char **oddity;
++extern unsigned char **oddity;
+ extern double **Vij;
+ 
+ /* This swaps any conductor orignally at -1 V to +1 V. Any
diff -Nru atlc-4.6.1/debian/patches/series atlc-4.6.1/debian/patches/series
--- atlc-4.6.1/debian/patches/series2017-12-30 04:06:57.0 +
+++ atlc-4.6.1/debian/patches/series2020-08-05 12:08:40.0 +0100
@@ -1,3 +1,4 @@
 atlc.1.patch
 lintian-fixes.diff
 lintian-fixes2.diff
+fix_ftbfs.patch

Processed: atlc: diff for NMU version 4.6.1-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 957019 + patch
Bug #957019 [src:atlc] atlc: ftbfs with GCC-10
Added tag(s) patch.
> tags 957019 + pending
Bug #957019 [src:atlc] atlc: ftbfs with GCC-10
Added tag(s) pending.

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

Processed: owner 966765

[Debian Bug Tracking System]

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

> owner 966765 !
Bug #966765 [src:obs-build] obs-build: Unversioned Python removal in 
sid/bullseye
Owner recorded as Andrej Shadura .
> thanks
Stopping processing here.

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

Bug#966885: marked as done (spring: FTBFS: SHA512.cpp:25:3: error: ‘snprintf’ was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 13:03:50 +
with message-id 
and subject line Bug#966885: fixed in spring 104.0+dfsg-7
has caused the Debian Bug report #966885,
regarding spring: FTBFS: SHA512.cpp:25:3: error: ‘snprintf’ was not declared in 
this scope
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.)


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

Hi,

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

Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/rts/builds/legacy && /usr/bin/c++  
> -DASIO_STANDALONE -DBOOST_ALL_NO_LIB -DBOOST_NO_FENV_H -DBOOST_REGEX_DYN_LINK 
> -DBOOST_SYSTEM_DYN_LINK 
> -DSPRING_DATADIR=\"/usr/share/games/spring:/usr/lib/spring\" -DSTREFLOP_SSE 
> -DSYNCCHECK -DTHREADPOOL -DUSE_LIBSQUISH -D_GLIBCXX_USE_NANOSLEEP 
> -D_RANDOM_TCC -I/<>/rts/lib/lua/include 
> -I/<>/include/AL -I/<>/rts 
> -I/<>/rts/lib/assimp/include 
> -I/<>/obj-x86_64-linux-gnu/src-generated/engine 
> -I/<>/obj-x86_64-linux-gnu/rts/lib/gflags/include 
> -I/usr/include/SDL2 -I/usr/include/freetype2 -I/usr/include/AL 
> -I/<>/rts/lib/asio/include 
> -I/<>/rts/lib/slimsig/include  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -std=gnu++11 
> -fdiagnostics-color=auto -mtune=generic -msse -mfpmath=sse -mno-sse2 
> -mno-sse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -mno-sse4 -mno-sse4a -mno-avx 
> -mno-fma -mno-fma4 -mno-xop -mno-lwp -mno-avx2 -fsingle-precision-constant 
> -frounding-math -mieee-fp -pipe -fno-strict-aliasing  -fvisibility=hidden  
> -fvisibility-inlines-hidden -pthread  -O2  -Wformat -Wformat-security 
> -DNDEBUG -g   -o 
> CMakeFiles/engine-legacy.dir/__/__/System/Platform/SharedLib.cpp.o -c 
> /<>/rts/System/Platform/SharedLib.cpp
> /<>/rts/System/Sync/SHA512.cpp: In function ‘void 
> sha512::dump_digest(const std::array&, std::array 129>&)’:
> /<>/rts/System/Sync/SHA512.cpp:25:3: error: ‘snprintf’ was not 
> declared in this scope
>25 |   snprintf(hex_chars.data() + (i * 2), hex_chars.size() - (i * 2), 
> "%02x", sha_bytes[i]);
>   |   ^~~~
> /<>/rts/System/Sync/SHA512.cpp:7:1: note: ‘snprintf’ is defined 
> in header ‘’; did you forget to ‘#include ’?
> 6 | #include "SHA512.hpp"
>   +++ |+#include 
> 7 | 
> make[4]: *** 
> [rts/builds/headless/CMakeFiles/engine-headless.dir/build.make:4174: 
> rts/builds/headless/CMakeFiles/engine-headless.dir/__/__/System/Sync/SHA512.cpp.o]
>  Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/spring_104.0+dfsg-6_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: spring
Source-Version: 104.0+dfsg-7
Done: Markus Koschany 

We believe that the bug you reported is fixed in the latest version of
spring, 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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated spring package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Aug 2020 14:05:12 +0200
Source: spring
Architecture: source
Version: 104.0+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Closes: 966885
Changes:
 spring (104.0+dfsg-7) unstable; urgency=medium
 .
   * Switch to debhelper-compat = 13.
   * Fix build failure with gcc 10 due to missing include.
 Thanks to Steve Langasek for the patch. (Closes: #966885)
Checksums-Sha1:
 6e54d99c7e8dd1d1de0a486c4ba1c87e89c89835 2519 spring_104.0+dfsg-7.dsc
 

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

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 13:03:38 +
with message-id 
and subject line Bug#966927: fixed in gammapy 0.17-2
has caused the Debian Bug report #966927,
regarding gammapy: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess 
returned exit status 2
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py clean 
> Compiling gammapy/stats/fit_statistics_cython.pyx because it depends on 
> /usr/lib/python3/dist-packages/Cython/Includes/numpy/__init__.pxd.
> [1/1] Cythonizing gammapy/stats/fit_statistics_cython.pyx
> running clean
> removing '/<>/.pybuild/cpython3_3.8_gammapy/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building gammapy using existing ./gammapy_0.17.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  gammapy-0.17/gammapy/stats/fit_statistics_cython.c
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/gammapy_0.17-1.diff.qQQCXp
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2020-08-02T17:22:09Z

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/gammapy_0.17-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: gammapy
Source-Version: 0.17-2
Done: Ole Streicher 

We believe that the bug you reported is fixed in the latest version of
gammapy, 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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated gammapy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Aug 2020 14:44:49 +0200
Source: gammapy
Architecture: source
Version: 0.17-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Closes: 966927
Changes:
 gammapy (0.17-2) unstable; urgency=medium
 .
   * Remove cythonized file. (Closes: #966927)
Checksums-Sha1:
 7236c007dc16403e70f1d72a105c442c82f89e0a 2501 gammapy_0.17-2.dsc
 9beb2b8cfbb563713341d77b8a7e36875a20cff0 5564 gammapy_0.17-2.debian.tar.xz
Checksums-Sha256:
 b64f42c8f2313575c45e4493a46e48e191d055a38a706089e9fef90ed50a2b9d 2501 
gammapy_0.17-2.dsc
 aa584bbdcff6a3f1521e1f8fa4b1c1c8d18986971242cddf8a81ce44928db3f3 5564 
gammapy_0.17-2.debian.tar.xz
Files:
 bf87c9151d10eda613dab1f8bcdea9b0 2501 python optional gammapy_0.17-2.dsc
 6675a4e947f787cf43d4e59397345467 5564 python optional 
gammapy_0.17-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAl8qqogACgkQmk9WvbkO
GL2+9w/8CZQxTPAVQTIDM2MddDVEWrQnQvfVmEzXgw2Dpb3XaCP0N2oxqLBh/JSo
uVmHoAe3V15N46yMJUPhiuB1zGJNve/Zo00EmC1TcJx44Wm/Pm4QeSM8fljkgfz1

Bug#966962: marked as done (flask-restful: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.8 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 13:03:33 +
with message-id 
and subject line Bug#966962: fixed in flask-restful 0.3.8-3
has caused the Debian Bug report #966962,
regarding flask-restful: FTBFS: dh_auto_test: error: pybuild --test --test-nose 
-i python{version} -p 3.8 returned exit code 13
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.)


-- 
966962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flask-restful
Version: 0.3.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 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 '/<>/docs'
> sphinx-build -b html -d _build/doctrees   . _build/html
> Running Sphinx v2.4.3
> making output directory... done
> loading intersphinx inventory from 
> /usr/share/doc/python-flask-doc/html/objects.inv...
> loading intersphinx inventory from 
> /usr/share/doc/python-werkzeug-doc/html/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory '/usr/share/doc/python-flask-doc/html/objects.inv' not 
> fetchable due to : [Errno 2] No such file or 
> directory: '/usr/share/doc/python-flask-doc/html/objects.inv'
> loading intersphinx inventory from 
> /usr/share/doc/python3-doc/html/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory '/usr/share/doc/python-werkzeug-doc/html/objects.inv' 
> not fetchable due to : [Errno 2] No such file or 
> directory: '/usr/share/doc/python-werkzeug-doc/html/objects.inv'
> loading intersphinx inventory from 
> /usr/share/doc/python3-doc/html/objects.inv...
> loading intersphinx inventory from six/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'six/objects.inv' not fetchable due to  'FileNotFoundError'>: [Errno 2] No such file or directory: 
> '/<>/docs/six/objects.inv'
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 9 source files that are out of date
> updating environment: [new config] 9 added, 0 changed, 0 removed
> reading sources... [ 11%] api
> reading sources... [ 22%] extending
> reading sources... [ 33%] fields
> reading sources... [ 44%] index
> reading sources... [ 55%] installation
> reading sources... [ 66%] intermediate-usage
> reading sources... [ 77%] quickstart
> reading sources... [ 88%] reqparse
> reading sources... [100%] testing
> 
> /<>/docs/index.rst:6: WARNING: duplicate object description of 
> flask_restful, other instance in api, use :noindex: for one of them
> /<>/docs/reqparse.rst:217: WARNING: Explicit markup ends without 
> a blank line; unexpected unindent.
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 11%] api
> writing output... [ 22%] extending
> writing output... [ 33%] fields
> writing output... [ 44%] index
> writing output... [ 55%] installation
> writing output... [ 66%] intermediate-usage
> writing output... [ 77%] quickstart
> writing output... [ 88%] reqparse
> writing output... [100%] testing
> 
> /<>/docs/intermediate-usage.rst:80: WARNING: undefined label: 
> blueprints (if the link has no caption the label must precede a section 
> header)
> /<>/docs/reqparse.rst:41: WARNING: undefined label: 
> error-messages (if the link has no caption the label must precede a section 
> header)
> generating indices...  genindex py-modindexdone
> writing additional pages...  searchdone
> copying static files... ... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 7 warnings.
> 
> The HTML pages are in _build/html.
> 
> Build finished. The HTML pages are in _build/html.
> make[2]: Leaving directory '/<>/docs'
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.8_flask-restful/build; python3.8 -m nose 
> -v tests
> test_accept_default_any_pick_first (tests.test_accept.AcceptTestCase) ... ok
> test_accept_default_application_json (tests.test_accept.AcceptTestCase) ... ok
> test_accept_default_override_accept (tests.test_accept.AcceptTestCase) ... ok
> test_accept_invalid_default_no_representations 
> (tests.test_accept.AcceptTestCase) ... ok
> 

Bug#964541: make: Regression on s390x, echo EPERM, caused by posix_spawn change

[Christian Borntraeger]

On 21.07.20 13:24, Julian Andres Klode wrote:
> On Tue, Jul 21, 2020 at 12:49:59PM +0200, Christian Borntraeger wrote:
>> On 21.07.20 10:18, Adrian Bunk wrote:
>>> [ adding debian-s390 to Cc ]
>>>
>>> On Wed, Jul 08, 2020 at 01:42:33PM +0200, Julian Andres Klode wrote:
 Package: make-dfsg
 Version: 4.3-4
 Severity: serious
 Tags: patch
 User: ubuntu-de...@lists.ubuntu.com
 Usertags: origin-ubuntu groovy ubuntu-patch

 In Ubuntu, the attached patch was applied to achieve the following:

 The autopkgtests for flatpak-builder/s390x where failing with

   echo Building
   make: echo: Operation not permitted
   make: *** [Makefile:2: all] Error 127
>>
>> Julian,
>>
>> is there a launchpad entry for the Ubuntu bug that was fixed by this change?
> 
> Yes, https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1886814, it's 
> also
> in the IBM bugzilla thingy - you can see Andreas Krebbel is replying to that.

FWIW, Stefan Liebler looked into this and this needs to be fixed in 
flatpak-build.
See the bug for details. 

Bug#966928: marked as done (python-biopython: FTBFS: AssertionError: 0.018551002172574885 != 0.0194 within 4 places (0.00084899782742511518 difference))

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 10:20:33 +
with message-id 
and subject line Bug#966928: fixed in python-biopython 1.77+dfsg-3
has caused the Debian Bug report #966928,
regarding python-biopython: FTBFS: AssertionError: 0.018551002172574885 != 
0.0194 within 4 places (0.00084899782742511518 difference)
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.)


-- 
966928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-biopython
Version: 1.77+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 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 '/<>'
> mkdir -p Tests_avoid
> for avoid in  PAML_tools EmbossPhylipNew MSAProbs_tool NACCESS_tool 
> PopGen_GenePop PopGen_GenePop_EasyController XXmotif_tool PDB_ResidueDepth 
> mmtf mmtf_online  BioSQL_MySQLdb BioSQL_psycopg2   \
>   ; do \
> mv Tests/test_${avoid}.py Tests_avoid ; \
> done
> # For the doc package we need a clean testsuite without all the remaining 
> files.  So keep a clean copy here
> mkdir -p debian/tmp_tests
> cp -a Tests debian/tmp_tests
> # remove duplicated file
> rm -f debian/tmp_tests/Tests/Quality/example.fastq.gz
> # We also keep the tests we need to avoid for later inspection
> cp -a Tests_avoid debian/tmp_tests
> # in the Debian package dialign it is not needed to set DIALIGN2_DIR but the 
> test is verifying this dir
> # to run the EMBOSS test test_Emboss also requires to have the environment 
> variable EMBOSS_ROOT set
> LC_ALL=C.UTF-8 dh_auto_test -- --test --system=custom \
>   --test-args='set -e; \
>  mkdir -p {build_dir}/home; \
>  mkdir -p {build_dir}/Doc/examples; \
>  cp -a Doc/Tutorial.tex {build_dir}/Doc; \
>  cp -a Doc/Tutorial {build_dir}/Doc; \
>  cp -a Doc/examples {build_dir}/Doc; \
>  cp -a Tests {build_dir}; \
>  cd {build_dir}/Tests; \
>  env DIALIGN2_DIR=/usr/share/dialign 
> EMBOSS_ROOT=/usr/lib/emboss HOME={build_dir}/home {interpreter} run_tests.py 
> --offline'
>   pybuild --test -i python{version} -p 3.8 --test --system=custom 
> "--test-args=set -e; \\\
>  mkdir -p {build_dir}/home; \\\
>  mkdir -p {build_dir}/Doc/examples; \\\
>  cp -a Doc/Tutorial.tex {build_dir}/Doc; \\\
>  cp -a Doc/Tutorial {build_dir}/Doc; \\\
>  cp -a Doc/examples {build_dir}/Doc; \\\
>  cp -a Tests {build_dir}; \\\
>  cd {build_dir}/Tests; \\\
>  env DIALIGN2_DIR=/usr/share/dialign 
> EMBOSS_ROOT=/usr/lib/emboss HOME={build_dir}/home {interpreter} run_tests.py 
> --offline"
> I: pybuild base:217: set -e; \
>  mkdir -p 
> /<>/.pybuild/cpython3_3.8/build/home; \
>  mkdir -p 
> /<>/.pybuild/cpython3_3.8/build/Doc/examples; \
>  cp -a Doc/Tutorial.tex 
> /<>/.pybuild/cpython3_3.8/build/Doc; \
>  cp -a Doc/Tutorial 
> /<>/.pybuild/cpython3_3.8/build/Doc; \
>  cp -a Doc/examples 
> /<>/.pybuild/cpython3_3.8/build/Doc; \
>  cp -a Tests 
> /<>/.pybuild/cpython3_3.8/build; \
>  cd 
> /<>/.pybuild/cpython3_3.8/build/Tests; \
>  env DIALIGN2_DIR=/usr/share/dialign 
> EMBOSS_ROOT=/usr/lib/emboss 
> HOME=/<>/.pybuild/cpython3_3.8/build/home python3.8 run_tests.py 
> --offline
> test_Ace ... ok
> test_Affy ... ok
> test_AlignIO ... ok
> test_AlignIO_ClustalIO ... ok
> test_AlignIO_EmbossIO ... ok
> test_AlignIO_FastaIO ... ok
> test_AlignIO_MauveIO ... ok
> test_AlignIO_PhylipIO ... ok
> test_AlignIO_convert ... ok
> test_AlignInfo ... ok
> test_Application ... ok
> test_BWA_tool ... ok
> test_BioSQL_MySQLdb_online ... skipping. internet not available
> test_BioSQL_mysql_connector ... skipping. BioSQL test configuration file 
> biosql.ini missing (see biosql.ini.sample)
> test_BioSQL_mysql_connector_online ... skipping. internet not available
> test_BioSQL_psycopg2_online ... skipping. internet not available
> 

Processed: Re: Bug#967117: aeskulap: Unversioned Python removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #967117 [src:aeskulap] aeskulap: Unversioned Python removal in sid/bullseye
Added tag(s) moreinfo.

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

Bug#967117: aeskulap: Unversioned Python removal in sid/bullseye

[Andreas Tille]

Control: tags -1 moreinfo

On Tue, Aug 04, 2020 at 09:27:37AM +, Matthias Klose wrote:
> Package: src:aeskulap
> Version: 0.2.2-beta2+git20190406.ef77f01-2
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2unversioned

I grepped the packaging git for the string python which has no hits
except in some irrelevant documentation file and checked the
dependencies of aeskulap but I can not find any reference to python.

Could you please explain this bug?

Kind regards and thanks for all your work in the Python migration

 Andreas.

-- 
http://fam-tille.de

Bug#967209: marked as done (rgtk2: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 5 Aug 2020 12:36:41 +0200
with message-id 
and subject line Re: Bug#967209: rgtk2: Unversioned Python removal in 
sid/bullseye
has caused the Debian Bug report #967209,
regarding rgtk2: Unversioned Python 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.)


-- 
967209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rgtk2
Version: 2.20.36-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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 ---
fixed libglade2 is now in the archive.

On 8/4/20 3:16 PM, Dirk Eddelbuettel wrote:
> 
> On 4 August 2020 at 15:06, Matthias Klose wrote:
> | block 967209 by 967157
> | thanks
> | 
> | sorry, that's due to uninstallability of libglade2-dev.
> 
> Thanks, that makes sense.
> 
> (And thanks also to Julien, that was a good idea too but it does come up
> negative:
> 
>   edd@rob:~/deb/rgtk2(master)$ grep -ri Python
>   inst/doc/tutorial.sgml:bindings for many other languages including C, C++, 
> Guile, Perl, Python,
>   edd@rob:~/deb/rgtk2(master)$ 
> 
> Dirk
> 
> | On 8/4/20 2:49 PM, Dirk Eddelbuettel wrote:
> | > 
> | > Hi doko and Python folks,
> | > 
> | > On 4 August 2020 at 09:29, Matthias Klose wrote:
> | > | Package: src:rgtk2
> | > | Version: 2.20.36-2
> | > | Severity: serious
> | > | Tags: sid bullseye
> | > | User: debian-pyt...@lists.debian.org
> | > | Usertags: py2unversioned
> | > | 
> | > | 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
> | > | 
> | > | We will keep some Python2 package as discussed in
> | > | https://lists.debian.org/debian-python/2020/07/msg00039.html
> | > | but removing the unversioned python packages python-minimal, python,
> | > | python-dev, python-dbg, python-doc.
> | > | 
> | > | Your package either build-depends, depends on one of those packages.
> | > | Please either convert these packages to Python3, or if that is not
> | > | possible, replaces the dependencies on the unversioned Python
> | > | packages with one of the python2 dependencies (python2, python2-dev,
> | > | python2-dbg, python2-doc).
> | > | 
> | > | Please check for dependencies, build dependencies AND autopkg tests.
> | > 
> | > I am lost.
> | > 
> | > Build-Depends:
> | >   Source: rgtk2
> | >   Section: gnu-r
> | >   Priority: optional
> | >   Maintainer: Dirk Eddelbuettel 
> | >   Build-Depends: debhelper (>= 10), dh-r (>= 20180615), r-base-dev (>= 
> 3.6.1), libgtk2.0-dev (>= 2.10.12), libglade2-dev, libpango1.0-dev, 
> libcairo2-dev
> | >   Standards-Version: 4.4.0
> | >   Vcs-Browser: https://salsa.debian.org/edd/r-cran-rgtk2
> | >   Vcs-Git: https://salsa.debian.org/edd/r-cran-rgtk2.git
> | >   Homepage: https://cran.r-project.org/package=RGtk2
> | > 
> | > Build-Depends: debhelper (>= 10), dh-r (>= 20180615), r-base-dev (>= 
> 3.6.1), libgtk2.0-dev (>= 2.10.12), libglade2-dev, libpango1.0-dev, 
> libcairo2-dev
> | > 
> | > Depends:
> | >   Package: r-cran-rgtk2
> | >   Source: rgtk2 (2.20.36-2)
> | >   Version: 2.20.36-2+b1
> | >   Installed-Size: 18722
> | >   Maintainer: Dirk Eddelbuettel 
> | >   Architecture: amd64
> | >   Depends: r-base-core (>= 4.0.0-3), r-api-4.0, libatk1.0-0 (>= 1.12.4), 
> libc6 (>= 2.14), libcairo2 (>= 1.8.0), libgdk-pixbuf2.0-0 (>= 2.22.0), 
> libglib2.0-0 (>= 2.41.1), libgtk2.0-0 (>= 2.20.0), libpango-1.0-0 (>= 
> 1.25.5), libpangocairo-1.0-0 (>= 1.22.0)
> | >   Description-en: GNU R 

Bug#963356: marked as done (cross-toolchain-base-mipsen: FTBFS: dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Wed, 5 Aug 2020 19:41:41 +0800
with message-id 
and subject line Re: cross-toolchain-base-mipsen: FTBFS: dpkg-buildpackage: 
error:  fakeroot debian/rules clean subprocess returned exit status 2
has caused the Debian Bug report #963356,
regarding cross-toolchain-base-mipsen: FTBFS: dpkg-buildpackage: error: 
fakeroot debian/rules clean subprocess returned exit status 2
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> debian/kernelarch.make:5: *** empty variable name.  Stop.
> dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
> exit status 2
> 
> Build finished at 2020-06-21T07:14:58Z

The full build log is available from:
   
http://qa-logs.debian.net/2020/06/20/cross-toolchain-base-mipsen_10_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 ---
On Sun, 21 Jun 2020 22:20:52 +0200 Lucas Nussbaum  wrote:
> Source: cross-toolchain-base-mipsen
> Version: 10
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200620 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 

This problem has been fixed in version 11.

> Relevant part (hopefully):
> >  fakeroot debian/rules clean
> > debian/kernelarch.make:5: *** empty variable name.  Stop.
> > dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
> > exit status 2
> > 
> > Build finished at 2020-06-21T07:14:58Z
> 
> The full build log is available from:
>
> http://qa-logs.debian.net/2020/06/20/cross-toolchain-base-mipsen_10_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 ---

Bug#967153: marked as done (krb5-auth-dialog: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 5 Aug 2020 14:38:10 +0200
with message-id <8750b29f-6394-33f9-96d9-916de170c...@debian.org>
and subject line Re: Bug#967153: krb5-auth-dialog: Unversioned Python removal 
in sid/bullseye
has caused the Debian Bug report #967153,
regarding krb5-auth-dialog: Unversioned Python 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.)


-- 
967153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:krb5-auth-dialog
Version: 3.26.1-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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 ---
On 8/5/20 1:56 PM, Guido Günther wrote:
> Hi,
> On Tue, Aug 04, 2020 at 09:28:15AM +, Matthias Klose wrote:
>> Package: src:krb5-auth-dialog
>> Version: 3.26.1-3
>> Severity: serious
>> Tags: sid bullseye
>> User: debian-pyt...@lists.debian.org
>> Usertags: py2unversioned
>>
>> 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
>>
>> We will keep some Python2 package as discussed in
>> https://lists.debian.org/debian-python/2020/07/msg00039.html
>> but removing the unversioned python packages python-minimal, python,
>> python-dev, python-dbg, python-doc.
>>
>> Your package either build-depends, depends on one of those packages.
>> Please either convert these packages to Python3, or if that is not
>> possible, replaces the dependencies on the unversioned Python
>> packages with one of the python2 dependencies (python2, python2-dev,
>> python2-dbg, python2-doc).
>>
>> Please check for dependencies, build dependencies AND autopkg tests.
> 
> Can you say how the list was generated? krb5-auth-dialog does not seem
> to depend on any of these.

that showed up because libglade2-dev was uninstallable. Closing.--- End Message ---

Processed: Bug#966885 marked as pending in spring

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #966885 [src:spring] spring: FTBFS: SHA512.cpp:25:3: error: ‘snprintf’ was 
not declared in this scope
Added tag(s) pending.

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

Bug#966885: marked as pending in spring

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #966885 in spring 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/games-team/spring/-/commit/e53b8e4b413013fd4860dc0bdbbfa2defe5445d7


Fix build failure with gcc 10 due to missing include.

Closes: #966885
Thanks: Steve Langasek for the patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/966885

Bug#967164: marked as done (liblemon: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 09:33:47 +
with message-id 
and subject line Bug#967164: fixed in liblemon 1.3.1+dfsg-4
has caused the Debian Bug report #967164,
regarding liblemon: Unversioned Python 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.)


-- 
967164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:liblemon
Version: 1.3.1+dfsg-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: liblemon
Source-Version: 1.3.1+dfsg-4
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
liblemon, 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 967...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated liblemon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Aug 2020 10:37:12 +0200
Source: liblemon
Architecture: source
Version: 1.3.1+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 967164
Changes:
 liblemon (1.3.1+dfsg-4) unstable; urgency=medium
 .
   * Build-Depends: s/python/python3/
 Closes: #967164
Checksums-Sha1:
 4a76aba5208f3b4914388b6fc4a43b91fa8db747 2244 liblemon_1.3.1+dfsg-4.dsc
 4a03ac51586bb4afc47b0d5358751bda659a4009 6144 
liblemon_1.3.1+dfsg-4.debian.tar.xz
 b5a3984df336ad3f63b6b45abf77f871df3dcc15 11343 
liblemon_1.3.1+dfsg-4_amd64.buildinfo
Checksums-Sha256:
 6e4abf9e1fa128db2c5f607f13e252964191242bcde6cc9de46b901de0454cdb 2244 
liblemon_1.3.1+dfsg-4.dsc
 9e9e6c74e22625941a3a6a4f2085013ac15bda4553b9e36ef074c961f39e05c1 6144 
liblemon_1.3.1+dfsg-4.debian.tar.xz
 a6f7e848581dbd8c18ea40e038ac6e5dd9511c40df481f25be37d3340a8880ba 11343 
liblemon_1.3.1+dfsg-4_amd64.buildinfo
Files:
 cf05de7ebf38b08a6595a327313c51e3 2244 science optional 
liblemon_1.3.1+dfsg-4.dsc
 66c2985f31d1a222fd966a6dda1e7000 6144 science optional 
liblemon_1.3.1+dfsg-4.debian.tar.xz
 adfc570c8b62ff0d4e6e143441db4aae 11343 science optional 
liblemon_1.3.1+dfsg-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl8qeK8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHJZQ//fSbupKf5GrJmK0lWctlRDA+66gBvElYG
TTYB7Py4eV7vPYSyj22p7P/AQ2SFySCggjpyZ2AMafSKgmjCj7Ww8v+RncHw/0ra
8YDiIqdqM1SwAuZWUm5J2Q4J8teJVQ0i0NIuNGI6JCObEB/AUpXQpxOQsXsSxYeX
0/iPM+nDMBQb33kBgRICwod8/QzCUfqnGj3cmH7oM0NvJuU8aOe8zMfLzDq+ypK8
f5WjouzC+Iug+bYOpqYvxv/tKPdSa4NCHrDIS9wk2e5NAAU27lIHFogW6F3hN0Yb
NZoMOXJxywS9x5xa3M7Ls/9z6KiUEmn0IjKmvycT2E/kc/CVe0rgC0m62MS714OW
Kjyb4hzLvT5ZJ9ZsrKYK6E/dX+rfofnASnvfqRwefUOoPo9/9Orqt6+ddhbILBrA
7klQTpDYQWf8Pd/m9o1MBz3k05swSDYsC5r7bQrW/JAoXhrv4myrG9B4RgZ7y/+J
UI4yZ6CqThhJHx1SYcvxDdSv8Mv/ZGCniwvuUTRU13oehfQy16NzY74hfjvrnAMh
aWMd6ILS3m0AffC1MFCkJCUR5ged14BPDgdfPkwjuev+cT2CfyewEFU1sH41Ppkl
FR4THMKv5eh+EHAsO0bRcs7NrZdONcT3yLiZ7GjV+xWwxDRhoh+MPNNrjdjIwbjL
72cOpsGaewQ=
=oYrq
-END PGP SIGNATURE End Message ---

Bug#967937: gimp-python: not installable: depends on "python"

[Adam Borowski]

Package: gimp-python
Version: 2.10.8-2+b1
Severity: grave
Justification: renders package unusable

Hi!
As the package "python" is no more, gimp-python can no longer be installed.
It needs to either depend on "python2" (in the short term) or, preferably,
be updated for py3.


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

Kernel: Linux 5.8.0-umbar-00027-gfee487f15878 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gimp-python depends on:
ii  libbabl-0.1-0   0.1.78-1
ii  libc6   2.31-3
ii  libgdk-pixbuf2.0-0  2.40.0+dfsg-5
ii  libgegl-0.4-0   0.4.24-1
ii  libgimp2.0  2.10.18-1
ii  libglib2.0-02.64.4-1
ii  libgtk2.0-0 2.24.32-4
**  python (hacked away in dpkg/status)
ii  python-gtk2 2.24.0-6
ii  python2.7   2.7.18-1

gimp-python recommends no packages.

gimp-python suggests no packages.

-- no debconf information

Processed: Re: Bug#966920: spoa: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #966920 [src:spoa] spoa: FTBFS: dpkg-gensymbols: error: some symbols or 
patterns disappeared in the symbols file: see diff output below
Ignoring request to alter tags of bug #966920 to the same tags previously set

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

Processed: Re: Bug#966920: spoa: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #966920 [src:spoa] spoa: FTBFS: dpkg-gensymbols: error: some symbols or 
patterns disappeared in the symbols file: see diff output below
Added tag(s) pending.

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

Bug#964294: marked as done (mlpack FTBFS: dh_missing: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 10:49:11 +
with message-id 
and subject line Bug#964294: fixed in mlpack 3.3.2-2
has caused the Debian Bug report #964294,
regarding mlpack FTBFS: dh_missing: error: missing files, aborting
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.)


-- 
964294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mlpack
Version: 3.3.2-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=mlpack

...
   dh_missing -a -O--buildsystem=cmake -O--max-parallel=1
dh_missing: warning: 
usr/lib/x86_64-linux-gnu/cmake/mlpack/mlpack-targets-none.cmake exists in 
debian/tmp but is not installed to anywhere
dh_missing: warning: usr/lib/x86_64-linux-gnu/cmake/mlpack/mlpack-targets.cmake 
exists in debian/tmp but is not installed to anywhere
dh_missing: warning: 
usr/lib/x86_64-linux-gnu/cmake/mlpack/mlpack-config-version.cmake exists in 
debian/tmp but is not installed to anywhere
dh_missing: warning: usr/lib/x86_64-linux-gnu/cmake/mlpack/mlpack-config.cmake 
exists in debian/tmp but is not installed to anywhere
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: libmlpack-dev (45), libmlpack3 (2), mlpack-bin (1), 
mlpack-doc (37), python3-mlpack (2)
 * dh_installdocs: libmlpack-dev (0), libmlpack3 (0), mlpack-bin (0), 
mlpack-doc (6), python3-mlpack (0)
 * dh_installexamples: libmlpack-dev (0), libmlpack3 (0), mlpack-bin 
(0), mlpack-doc (1), python3-mlpack (0)
 * dh_installman: libmlpack-dev (0), libmlpack3 (0), mlpack-bin (47), 
mlpack-doc (0), python3-mlpack (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
For a short-term work-around: Add the files to debian/not-installed
make: *** [debian/rules:46: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: mlpack
Source-Version: 3.3.2-2
Done: b...@debian.org (Barak A. Pearlmutter)

We believe that the bug you reported is fixed in the latest version of
mlpack, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Barak A. Pearlmutter  (supplier of updated mlpack 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, 04 Aug 2020 13:39:14 +0100
Source: mlpack
Architecture: source
Version: 3.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Barak A. Pearlmutter 
Closes: 962533 964294
Changes:
 mlpack (3.3.2-2) unstable; urgency=medium
 .
   * include cmake support files in development package (closes: #964294)
   * update configuration options, including enabling building of tests
   * enable Julia bindings
   * avoid compile-time resource exhaustion by using CLANG instead of GCC
 (closes: #962533)
   * quilt patch for build-killing LaTeX markup typo
   * install stray html support file
   * Now formula.repository is gone, huh
Checksums-Sha1:
 e1dbc0047e53d84b9369cb4d153e0452cbb3f1dd 2597 mlpack_3.3.2-2.dsc
 212c7311e3242b8c68552c499cebc0a64f062851 10440 mlpack_3.3.2-2.debian.tar.xz
 a56f9a32de5aa2c12663e8c1a0e41f2691deff1d 11698 mlpack_3.3.2-2_source.buildinfo
Checksums-Sha256:
 4aa0fea272570ff7130cf457eb565b9f280a823d59169e8b49494076c8512d3d 2597 
mlpack_3.3.2-2.dsc
 d515a00a7280b351e1053a2e6219c011f6762987a16a1e181d36296bf4aaa912 10440 
mlpack_3.3.2-2.debian.tar.xz
 f4087d3635ece131938932f03fc76a8c9f677f14e95d191182084f5f85a30a7b 11698 
mlpack_3.3.2-2_source.buildinfo
Files:
 fea31a0d8bbb5404a5a3cc4f4f9e9907 2597 libs optional mlpack_3.3.2-2.dsc
 

Bug#967012: vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern

[Adam Borowski]

Control: block -1 by 964457

On Mon, Aug 03, 2020 at 01:19:42PM +0200, Lucas Nussbaum wrote:
> Source: vmem
> Version: 1.8-1
> Severity: serious

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

> > vmem_aligned_alloc@@LIBVMEM_1.0
> > vmem_calloc@@LIBVMEM_1.0

Another case of a test failing due to bogus decoration.

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ It's time to migrate your Imaginary Protocol from version 4i to 6i.
⠈⠳⣄

Bug#966983: python-skbio: FTBFS: dh_sphinxdoc: error: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/search.html does not load searchindex.js

[Andreas Tille]

Control: tags -1 unreproducible

On Mon, Aug 03, 2020 at 11:05:59AM +0200, Lucas Nussbaum wrote:
> Source: python-skbio
> Version: 0.5.6-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200802 ftbfs-bullseye
...
> > dh_sphinxdoc --package=python-skbio-doc
> > dh_sphinxdoc: error: 
> > debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/search.html 
> > does not load searchindex.js
> > make[1]: *** [debian/rules:41: override_dh_sphinxdoc] Error 25

I tried to reproduce this bug I get:

dh_sphinxdoc --package=python-skbio-doc
dh_sphinxdoc: warning: ignoring unknown JavaScript code: 
debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/bootstrap-sphinx.js
dh_sphinxdoc: warning: ignoring unknown JavaScript code: 
debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/copybutton.js
dh_sphinxdoc: warning: ignoring unknown JavaScript code: 
debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/MathJax.js
dh_sphinxdoc: warning: ignoring unknown JavaScript code: 
debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/bootstrap-3.3.7/js/bootstrap.min.js
dh_sphinxdoc: warning: ignoring unknown JavaScript code: 
debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/js/jquery-fix.js
dh_sphinxdoc: warning: ignoring unknown JavaScript code: 
debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/js/jquery-1.11.0.min.js

 
No error so far.  Thus I'm tempted to close this bug.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#967153: krb5-auth-dialog: Unversioned Python removal in sid/bullseye

[Guido Günther]

Hi,
On Tue, Aug 04, 2020 at 09:28:15AM +, Matthias Klose wrote:
> Package: src:krb5-auth-dialog
> Version: 3.26.1-3
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2unversioned
> 
> 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
> 
> We will keep some Python2 package as discussed in
> https://lists.debian.org/debian-python/2020/07/msg00039.html
> but removing the unversioned python packages python-minimal, python,
> python-dev, python-dbg, python-doc.
> 
> Your package either build-depends, depends on one of those packages.
> Please either convert these packages to Python3, or if that is not
> possible, replaces the dependencies on the unversioned Python
> packages with one of the python2 dependencies (python2, python2-dev,
> python2-dbg, python2-doc).
> 
> Please check for dependencies, build dependencies AND autopkg tests.

Can you say how the list was generated? krb5-auth-dialog does not seem
to depend on any of these.
Cheers,
 -- Guido

> 
> 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.

Bug#957941: marked as done (wmcalclock: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 12:05:21 +
with message-id 
and subject line Bug#957941: fixed in wmcalclock 1.25-16.1
has caused the Debian Bug report #957941,
regarding wmcalclock: ftbfs with GCC-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.)


-- 
957941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wmcalclock
Version: 1.25-16
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/wmcalclock_1.25-16_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
SCHROOT_ALIAS_NAME=unstable
SCHROOT_CHROOT_NAME=sid-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-dd0a9ef6-63cd-4fa8-a84e-53db93ccd861
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package wmcalclock
dpkg-buildpackage: info: source version 1.25-16
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Kevin Coyner 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -rf build-stamp install-stamp ./debian/wmcalclock
find ./Src -name '*.o' | xargs rm -f
make -C Src clean
make[1]: Entering directory '/<>/Src'
for i in wmCalClock.o xutils.o ; do \
rm -f $i; \
done
rm -f wmCalClock
make[1]: Leaving directory '/<>/Src'
dh_clean
 debian/rules build
dh_testdir
make -C Src CFLAGS="-W -Wall -O2"
make[1]: Entering directory '/<>/Src'
x86_64-linux-gnu-gcc -W -Wall -O2 -DLinux -c wmCalClock.c -o wmCalClock.o 
-I/usr/X11R6/include/X11 -I/usr/X11R6/include
wmCalClock.c: In function ‘ButtonPressEvent.part.0.isra’:
wmCalClock.c:1034:27: warning: ‘%s’ directive writing up to 1023 bytes into a 
region of size 512 [-Wformat-overflow=]
 1034 | sprintf(Command, "%s &", ExecuteCommand);
  |   ^~ ~~
wmCalClock.c:1034:9: note: ‘sprintf’ output between 3 and 1026 bytes into a 
destination of size 512
 1034 | sprintf(Command, "%s &", ExecuteCommand);
  | ^~~~
wmCalClock.c: In function ‘main’:
wmCalClock.c:626:7: warning: ‘D[7]’ may be used uninitialized in this function 
[-Wmaybe-uninitialized]
  626 |   copyXPMArea(xsDigits[digit], yDigits, xdDigits[digit], ydDigits, 
xoff+extradx, 7+extrady);
  |   
^
wmCalClock.c:623:24: warning: ‘D[6]’ may be used uninitialized in this function 
[-Wmaybe-uninitialized]
  623 |   xoff += (xdDigits[digit]+1);
  |^~~
x86_64-linux-gnu-gcc -W -Wall -O2 -DLinux -c xutils.c -o xutils.o 
-I/usr/X11R6/include/X11 -I/usr/X11R6/include
xutils.c: In function ‘initXwindow’:
xutils.c:139:22: warning: unused parameter ‘argc’ [-Wunused-parameter]
  139 | void initXwindow(int argc, char *argv[]){
  |  ^~~~
x86_64-linux-gnu-gcc   -o wmCalClock wmCalClock.o xutils.o 
-I/usr/X11R6/include/X11 -I/usr/X11R6/include -L/usr/X11R6/lib -lXpm -lX11 
-lXext
/usr/bin/ld: xutils.o:(.bss+0x1e8): multiple definition of `iconwin'; 
wmCalClock.o:(.bss+0x8e0): first defined here
/usr/bin/ld: xutils.o:(.bss+0x1f8): multiple definition of `display'; 
wmCalClock.o:(.bss+0x8f0): first defined here

Bug#957849: marked as done (sup: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 12:20:49 +
with message-id 
and subject line Bug#957849: fixed in sup 20100519-3
has caused the Debian Bug report #957849,
regarding sup: ftbfs with GCC-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.)


-- 
957849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sup
Version: 20100519-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/sup_20100519-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean
dh: warning: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_auto_clean
dh_auto_clean: warning: Compatibility levels before 9 are deprecated (level 7 
in use)
make -j1 distclean
make[1]: Entering directory '/<>'
rm -f sup supscan supfilesrv libextra.a netcrypt.c *.o core a.out
make[1]: Leaving directory '/<>'
   dh_clean
dh_clean: warning: Compatibility levels before 9 are deprecated (level 7 in use)
 debian/rules build
dh build
dh: warning: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config
   dh_auto_configure
dh_auto_configure: warning: Compatibility levels before 9 are deprecated (level 
7 in use)
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- DEBIANCFLAGS="" SITE=LINUX
dh_auto_build: warning: Compatibility levels before 9 are deprecated (level 7 
in use)
make -j1 DEBIANCFLAGS= SITE=LINUX
make[2]: Entering directory '/<>'
cc -UCMUCS -UCMU  -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR 
-DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o supcmain.o supcmain.c
cc -UCMUCS -UCMU  -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR 
-DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o supcvers.o supcvers.c
cc -UCMUCS -UCMU  -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR 
-DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o supcparse.o supcparse.c
cc -UCMUCS -UCMU  -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR 
-DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o supcname.o supcname.c
cc -UCMUCS -UCMU  -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR 
-DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o supcmisc.o supcmisc.c
cc -UCMUCS -UCMU  -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR 
-DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o supcmeat.o supcmeat.c
cc -UCMUCS -UCMU  -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR 
-DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o scm.o scm.c
scm.c: In function ‘service’:
scm.c:316:2: warning: implicit declaration of function ‘setproctitle’ 
[-Wimplicit-function-declaration]
  316 |  setproctitle("Serving %s", remotehost());
  |  ^~~~
cc -UCMUCS -UCMU  -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR 
-DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o scmio.o scmio.c
cc -UCMUCS -UCMU  -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR 
-DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o stree.o stree.c
cc -UCMUCS -UCMU  -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR 
-DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o log.o log.c
cc -UCMUCS -UCMU  -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR 
-DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o supmsg.o supmsg.c
[ Using netcryptvoid.c ]
cp netcryptvoid.c netcrypt.c
cc -UCMUCS -UCMU  -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR 
-DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o netcrypt.o netcrypt.c
cc -UCMUCS -UCMU  -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR 

Bug#966765: obs-build: Unversioned Python removal in sid/bullseye

[Dimitri John Ledkov]

On Sun, 02 Aug 2020 13:18:51 + Matthias Klose  wrote:
> Package: src:obs-build
> Version: 20180831-3
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2unversioned
>
> 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
>
> We will keep some Python2 package as discussed in
> https://lists.debian.org/debian-python/2020/07/msg00039.html
> but removing the unversioned python packages python-minimal, python,
> python-dev, python-dbg, python-doc.
>
> Your package either build-depends, depends on one of those packages.
> Please either convert these packages to Python3, or if that is not
> possible, replaces the dependencies on the unversioned Python
> packages with one of the python2 dependencies (python2, python2-dev,
> python2-dbg, python2-doc).
>
> Please check for dependencies, build dependencies AND autopkg tests.
>
> 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.
>
>

This is obsolete version of obs-build which is no longer used or
maintained upstream. It has long moved on to python3 version, which
are still not packaged yet in Debian.

Ditto other things in the same stack i.e. dnf / zypper / yum / rpm.

Please RM obs-build, and somebody who still cares about OBS tooling in
Debian might want to repackage this.

Note that OBS upstream do provide Debian & Ubuntu repositories with up
to date tooling, which is readily available and at this point in time,
recommended to be used.

I've stopped using OBS years ago.

-- 
Regards,

Dimitri.

Bug#966765: obs-build: Unversioned Python removal in sid/bullseye

[Andrej Shadura]

On Wed, 5 Aug 2020, at 14:39, Dimitri John Ledkov wrote:
> On Sun, 02 Aug 2020 13:18:51 + Matthias Klose  wrote:
> > Package: src:obs-build
> > Version: 20180831-3
> > Severity: serious
> > Tags: sid bullseye
> > User: debian-pyt...@lists.debian.org
> > Usertags: py2unversioned
> >
> > 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
> >
> > We will keep some Python2 package as discussed in
> > https://lists.debian.org/debian-python/2020/07/msg00039.html
> > but removing the unversioned python packages python-minimal, python,
> > python-dev, python-dbg, python-doc.
> >
> > Your package either build-depends, depends on one of those packages.
> > Please either convert these packages to Python3, or if that is not
> > possible, replaces the dependencies on the unversioned Python
> > packages with one of the python2 dependencies (python2, python2-dev,
> > python2-dbg, python2-doc).
> >
> > Please check for dependencies, build dependencies AND autopkg tests.
> >
> > 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.
> >
> >
> 
> This is obsolete version of obs-build which is no longer used or
> maintained upstream. It has long moved on to python3 version, which
> are still not packaged yet in Debian.
> 
> Ditto other things in the same stack i.e. dnf / zypper / yum / rpm.
> 
> Please RM obs-build, and somebody who still cares about OBS tooling in
> Debian might want to repackage this.

Please don't RM it, I'll update it shortly.

> Note that OBS upstream do provide Debian & Ubuntu repositories with up
> to date tooling, which is readily available and at this point in time,
> recommended to be used.
> 
> I've stopped using OBS years ago.
> 
> -- 
> Regards,
> 
> Dimitri.
> 
>

-- 
Cheers,
  Andrej

Bug#967171: marked as done (mdk: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 5 Aug 2020 12:39:27 +0200
with message-id 
and subject line Re: Bug#967171: mdk: Unversioned Python removal in sid/bullseye
has caused the Debian Bug report #967171,
regarding mdk: Unversioned Python 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.)


-- 
967171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mdk
Version: 1.2.10+dfsg-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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 ---
closing, fixed libglade2 is now in the archive.

On 8/4/20 1:13 PM, Peter Pentchev wrote:
> block 967171 by 967157
> thanks
> 
> On Tue, Aug 04, 2020 at 09:28:34AM +, Matthias Klose wrote:
>> Package: src:mdk
>> Version: 1.2.10+dfsg-3
>> Severity: serious
>> Tags: sid bullseye
>> User: debian-pyt...@lists.debian.org
>> Usertags: py2unversioned
>>
>> 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
> 
> Hi,
> 
> Thanks for filing this one! I believe that it will be automagically
> fixed along with #967157, which you already took care of earlier today
> :)
> 
> Keeping this one open for now, of course...
> 
> G'luck,
> Peter
> --- End Message ---

Bug#967117: marked as done (aeskulap: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 5 Aug 2020 12:38:44 +0200
with message-id 
and subject line Re: Bug#967117: aeskulap: Unversioned Python removal in 
sid/bullseye
has caused the Debian Bug report #967117,
regarding aeskulap: Unversioned Python 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.)


-- 
967117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aeskulap
Version: 0.2.2-beta2+git20190406.ef77f01-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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 ---
closing, libglade2-dev (depending on python) was uninstallable.

On 8/5/20 12:37 PM, Andreas Tille wrote:
> Control: tags -1 moreinfo
> 
> On Tue, Aug 04, 2020 at 09:27:37AM +, Matthias Klose wrote:
>> Package: src:aeskulap
>> Version: 0.2.2-beta2+git20190406.ef77f01-2
>> Severity: serious
>> Tags: sid bullseye
>> User: debian-pyt...@lists.debian.org
>> Usertags: py2unversioned
> 
> I grepped the packaging git for the string python which has no hits
> except in some irrelevant documentation file and checked the
> dependencies of aeskulap but I can not find any reference to python.
> 
> Could you please explain this bug?
> 
> Kind regards and thanks for all your work in the Python migration
> 
>  Andreas.
> --- End Message ---

Bug#966920: spoa: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

[Andreas Tille]

Control: tags -1 pending

Package that is fixing this issue was uploaded to new
   https://ftp-master.debian.org/new/spoa_3.4.0-1.html

Kind regards, Andreas.

Bug#966864: marked as done (libiscsi: FTBFS: ld: .libs/libiscsi_la-iser.o:./lib/./../include/iser-private.h:162: multiple definition of `__packed'; .libs/libiscsi_la-init.o:./lib/./../include/iser-pri

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 11:03:45 +
with message-id 
and subject line Bug#966864: fixed in libiscsi 1.19.0-2
has caused the Debian Bug report #966864,
regarding libiscsi: FTBFS: ld: 
.libs/libiscsi_la-iser.o:./lib/./../include/iser-private.h:162: multiple 
definition of `__packed'; 
.libs/libiscsi_la-init.o:./lib/./../include/iser-private.h:162: first defined 
here
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.)


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

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=link gcc -Wall -W -Wshadow 
> -Wstrict-prototypes -Wpointer-arith -Wcast-align -Wno-strict-aliasing 
> -Wno-unknown-warning-option -Wno-stringop-truncation -Wwrite-strings -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -version-info 7:0:0 -bindir /usr/bin -no-undefined 
> -export-symbols ./libiscsi.syms -libverbs -lrdmacm -lpthread -Wl,-z,relro 
> -Wl,-z,now -o libiscsi.la -rpath /usr/lib/x86_64-linux-gnu 
> libiscsi_la-connect.lo libiscsi_la-crc32c.lo libiscsi_la-discovery.lo 
> libiscsi_la-init.lo libiscsi_la-login.lo libiscsi_la-nop.lo 
> libiscsi_la-pdu.lo libiscsi_la-iscsi-command.lo libiscsi_la-scsi-lowlevel.lo 
> libiscsi_la-socket.lo libiscsi_la-sync.lo libiscsi_la-task_mgmt.lo 
> libiscsi_la-logging.lo libiscsi_la-md5.lo libiscsi_la-iser.lo  
> libtool: link: echo "{ global:" > .libs/libiscsi.ver
> libtool: link:  cat ./libiscsi.syms | sed -e "s/\(.*\)/\1;/" >> 
> .libs/libiscsi.ver
> libtool: link:  echo "local: *; };" >> .libs/libiscsi.ver
> libtool: link:  gcc -shared  -fPIC -DPIC  .libs/libiscsi_la-connect.o 
> .libs/libiscsi_la-crc32c.o .libs/libiscsi_la-discovery.o 
> .libs/libiscsi_la-init.o .libs/libiscsi_la-login.o .libs/libiscsi_la-nop.o 
> .libs/libiscsi_la-pdu.o .libs/libiscsi_la-iscsi-command.o 
> .libs/libiscsi_la-scsi-lowlevel.o .libs/libiscsi_la-socket.o 
> .libs/libiscsi_la-sync.o .libs/libiscsi_la-task_mgmt.o 
> .libs/libiscsi_la-logging.o .libs/libiscsi_la-md5.o .libs/libiscsi_la-iser.o  
>  -libverbs -lrdmacm -lpthread  -g -O2 -fstack-protector-strong -Wl,-z 
> -Wl,relro -Wl,-z -Wl,now   -Wl,-soname -Wl,libiscsi.so.7 -Wl,-version-script 
> -Wl,.libs/libiscsi.ver -o .libs/libiscsi.so.7.0.0
> /usr/bin/ld: .libs/libiscsi_la-iser.o:./lib/./../include/iser-private.h:162: 
> multiple definition of `__packed'; 
> .libs/libiscsi_la-init.o:./lib/./../include/iser-private.h:162: first defined 
> here
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/libiscsi_1.19.0-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: libiscsi
Source-Version: 1.19.0-2
Done: Michael Tokarev 

We believe that the bug you reported is fixed in the latest version of
libiscsi, 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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated libiscsi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Aug 2020 13:40:02 +0300
Source: libiscsi
Architecture: source
Version: 1.19.0-2
Distribution: unstable
Urgency: medium
Maintainer: Michael Tokarev 
Changed-By: Michael Tokarev 
Closes: 966864
Changes:
 libiscsi (1.19.0-2) unstable; urgency=medium
 .
   * attribute_packed.patch (Closes: #966864)
   * spelling.patch - fix a few selling mistakes
   * provide Build-Depends-Package for libiscsi.symbols
   * do not 

Bug#967156: marked as done (ledger: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 11:18:44 +
with message-id 
and subject line Bug#967156: fixed in ledger 3.2.1-2
has caused the Debian Bug report #967156,
regarding ledger: Unversioned Python 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.)


-- 
967156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ledger
Version: 3.2.1-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: ledger
Source-Version: 3.2.1-2
Done: David Bremner 

We believe that the bug you reported is fixed in the latest version of
ledger, 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 967...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Bremner  (supplier of updated ledger package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Aug 2020 07:46:45 -0300
Source: ledger
Architecture: source
Version: 3.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: David Bremner 
Changed-By: David Bremner 
Closes: 843112 967156
Changes:
 ledger (3.2.1-2) unstable; urgency=medium
 .
   * Bug fix: "Unversioned Python removal in sid/bullseye", thanks to
 Matthias Klose (Closes: #967156).
   * Bug fix: "ledger deb package should suggest ledger-el", thanks to
 Thierry (Closes: #843112).
Checksums-Sha1:
 7ab04cfd0118817f6d4af06c32f6460a9e276aef 2251 ledger_3.2.1-2.dsc
 cf314e13325f2b5646b86b31059e5aabf611510c 7744 ledger_3.2.1-2.debian.tar.xz
 5761c9507bf6816897a6bcd5a0a755dbcdbed510 584624 ledger_3.2.1.orig.tar.xz
Checksums-Sha256:
 67ab59b157db4bf5fbb04862e266c36b89308837a4e0fdf9b639c29baf4b61b4 2251 
ledger_3.2.1-2.dsc
 332310b6dfd37833e4549132d8176913d15727e37609313642492b0f7a82a19a 7744 
ledger_3.2.1-2.debian.tar.xz
 27dea60c2a314e59f2144365de3b0f4ad33ef72ea408046d58d475b61537a8d6 584624 
ledger_3.2.1.orig.tar.xz
Files:
 60bbee567744c3a06017b5a1f49771a1 2251 utils optional ledger_3.2.1-2.dsc
 a03bcad8bcdb124edafa7bf9567cdf07 7744 utils optional 
ledger_3.2.1-2.debian.tar.xz
 5dd2c2d5730e3ce959ea8ade0eda2519 584624 utils optional ledger_3.2.1.orig.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl8qj+kACgkQA0U5G1Wq
FSGdqRAAqejB3LoAFq5qChJis/kYA5yyhbDQkvebKfWIyFIjqSOk8WbfbZ/q/Tdm
1ydrdIfnRSJik+Pp1+n2Cs2A0uRjswfXjrS7WvQeve/0SlS6OiooYfCXQu3Q2Mag
awxavI7SCXQ5Cg3jPArrp5Etfm984kyOLonU0Wt5dIWTtjouJdlflAjyAS5WwLGg
wAXoeNcXoI8GNH4vIl8i339RZuE+J9wG8ZvN1QF1t0AS+wBl1TslPjqXrH79YXkx
+LNp5RfSmv+ij0P/vPxMijK7AVDU4K9f8Va3OmLD/Q7Y+BWWdFbwirgh8Jfo6X/h
Hwqor+pM2T/Yg5j5Pf8tJG5TKSI0PcV0jMsZlUQGhvRVN+WUqI4/NpEENOgg2pHH
+AB/LWy3Pn9HXPGsZBo+TNJ3Hbuub2zpgdrO2jdFFkszT76BI8q1q3pdJ80BMGkW
yBDyq3/zjE4KK9NBrlkef/lB3Vb+iA6j21aI9QxVxN/nUFqBbsI0fWkMlNOFPz9q
g0kl9Mzezo2fNE2QGTUyFWv/Fbf/IbZLtN26F1gO6AaP+EIvgQBgV7VDty4ha4Fg
+DYjP4C+22IQ2xRkoww43ClwLBdLBykQ7aIeXMIWQSk/zESGO0s3BYBOcFzuk1d+
eZ6blaT3wFUMB5a4WjdQOk/Tl3sBOGRSYvn3skYd0Fyk3tskc+k=
=bqbp
-END PGP SIGNATURE End Message ---

Bug#966575: How to fix LLVM/LUKS installs?

[Dorian Gaensslen]

I.d.k. if it helps:

We had problems on many Systems (all of them used noninteractive 
installation method)

We saw, that if we do debconf-show grub-pc it showed us a wrong device:
 grub2/update_nvram: true
  grub-pc/install_devices_failed: false
  grub2/force_efi_extra_removable: false
* grub2/linux_cmdline: debian-installer=en_US
  grub-pc/kopt_extracted: false
* grub2/linux_cmdline_default: quiet
  grub-pc/install_devices_disks_changed:
  grub2/kfreebsd_cmdline:
  grub-pc/install_devices_failed_upgrade: true
  grub2/kfreebsd_cmdline_default: quiet
  grub-pc/mixed_legacy_and_grub2: true
  grub-pc/hidden_timeout: false
* grub-pc/install_devices: /dev/vda
  grub-pc/install_devices_empty: false
  grub-pc/partition_description:
  grub-pc/postrm_purge_boot_grub: false
  grub-pc/disk_description:
  grub-pc/timeout: 5
  grub-pc/chainload_from_menu.lst: true

* should be /dev/xvda

if we start the installer manually (interactive) the output is like this

* grub-pc/install_devices_disks_changed: /dev/xvda
 grub2/kfreebsd_cmdline:
  grub-pc/mixed_legacy_and_grub2: true
  grub-pc/kopt_extracted: false
  grub-pc/hidden_timeout: false
  grub-pc/partition_description:
  grub2/kfreebsd_cmdline_default: quiet
  grub-pc/timeout: 5
* grub2/linux_cmdline: debian-installer=en_US apparmor=1 
security=apparmor

  grub-pc/disk_description:
  grub-pc/install_devices_empty: false
* grub-pc/install_devices: /dev/xvda
  grub-pc/chainload_from_menu.lst: true
  grub2/force_efi_extra_removable: false
  grub-pc/postrm_purge_boot_grub: false
  grub-pc/install_devices_failed_upgrade: true
* grub2/linux_cmdline_default: quiet
  grub2/update_nvram: true
  grub-pc/install_devices_failed: false


with the last output the system worked flawlessly

strangely we had no problems whatsoever with systems which where major 
upgraded to buster.


All the Best
Dorian

Bug#966928: python-biopython: FTBFS: AssertionError: 0.018551002172574885 != 0.0194 within 4 places (0.00084899782742511518 difference)

[Andreas Tille]

On Mon, Aug 03, 2020 at 11:15:02PM +0200, Étienne Mollier wrote:
> Control: tags -1 fixed-upstream

Thanks for your research - I just uploaded with the pull request
connected patches to get rid of the nasty RC bug as soon as possible.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#966483: iptables-netflow: sourcing of external scripts in dkms file?

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #966483 [src:iptables-netflow] iptables-netflow: sourcing of external 
scripts in dkms file?
Severity set to 'normal' from 'serious'
> tag -1 - patch
Bug #966483 [src:iptables-netflow] iptables-netflow: sourcing of external 
scripts in dkms file?
Removed tag(s) patch.

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

Bug#966483: iptables-netflow: sourcing of external scripts in dkms file?

[Axel Beckert]

Control: severity -1 normal
Control: tag -1 - patch

Dear Gianfranco,

first thanks for making me aware of suboptimal upstream code.

Gianfranco Costamagna wrote:
> Hello, looks like your dkms ship file is sourcing external stuff
> with pushd/popd and so on.

Not "external" stuff but stuff from its own source.

> I don't think this is a sane idea,

I disagree. Using pushd/popd (or "cd -") in scripts is a valid way to
avoid a helper variable to save the previous directory.

But what I dislike in the aforementioned code snippet is that
$BASH_SOURCE is

a) used at all and hence the script is not bourne-shell compatible.
b) is used in an unclear way (couldn't find in bash(1) what the
   meaning of using an array as scalar should return. From my
   experiments, it seems to return its first value.)

I also disagree that "I don't think this is a sane idea" is RC-level,
not even important. Hence downgrading to "normal.

> specially because in Debian we don't even use version.sh script to
> fill the dkms.conf file.

I don't understand what you refer to with "in Debian". Do you mean the
fact that I didn't ship the package's upstream's version.sh? Do you
think I should?

> Can you please remove the two lines?

At least not in the way you propsed. Hence removing the tag "patch".

> this is what we do to test dkms packages:
[...]
> dkms_pkg=$(bash -c ". $dkms_conf; echo \$PACKAGE_NAME" 2>/dev/null)
> dkms_ver=$(bash -c ". $dkms_conf; echo \$PACKAGE_VERSION" 2>/dev/null)

You could do ". $dkms_conf > /dev/null"

> bash -c ". dkms.conf; echo \$PACKAGE_NAME"
> /tmp/iptables-netflow-2.5 /tmp/iptables-netflow-2.5
> /tmp/iptables-netflow-2.5
> ipt-netflow

JFTR: This can also happen with "cd", depending on the shell's
settings. (IIRC setting CDPATH might cause this. Granted, "bash -c" is
probably neither an interactive nor an login shell and hence shouldn't
source any local rc files, but I've ran into this with "cd" and some
non-DKMS scripts, too, on some machines not administrated by myself.

> I think dkms.conf files are meant to be sourced from outside, and
> launching scripts is a bad idea.

I don't see how this relates.

> --- iptables-netflow-2.5.orig/dkms.conf
> +++ iptables-netflow-2.5/dkms.conf
> @@ -1,7 +1,5 @@
>  PACKAGE_NAME="ipt-netflow"
> -pushd `dirname $BASH_SOURCE`
>  PACKAGE_VERSION=`./version.sh`
> -popd

IMHO this makes it worse, because it will source version.sh from
whatever working directory the script that sources dkms.conf was
called from.

I see these ways to solve this:

* Remove that whole block including "PACKAGE_VERSION=`./version.sh`",
  or
* make pushd/popd silent

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: bug 966436 is forwarded to https://github.com/ImageMagick/ImageMagick6/issues/90

[Debian Bug Tracking System]

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

> forwarded 966436 https://github.com/ImageMagick/ImageMagick6/issues/90
Bug #966436 [src:imagemagick] scrambled property in identify -verbose output
Set Bug forwarded-to-address to 
'https://github.com/ImageMagick/ImageMagick6/issues/90'.
> thanks
Stopping processing here.

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

Bug#962596: ca-certificates: Removal of GeoTrust Global CA requires investigation

[Michael Prokop]

* Thomas Goirand [Wed Jul 15, 2020 at 02:48:20PM +0200]:

> Thanks for maintaining ca-certificates.

> I just wanted to let you know that a number of customers of $work are
> affected by this, and we would very much welcome a return of the
> GeoTrust Global CA.

> It'd be nice if the uploaders of the ca-certificates could state what
> they intend to do, so we could take the appropriate measure locally.

Is there any news or timeline, or is there something we could help
with to get this sorted out, Michael (Shuler)?

regards
-mika-


signature.asc
Description: Digital signature

Bug#957223: marked as done (foxtrotgps: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 15:48:36 +
with message-id 
and subject line Bug#957223: fixed in foxtrotgps 1.2.2+bzr324-1
has caused the Debian Bug report #957223,
regarding foxtrotgps: ftbfs with GCC-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.)


-- 
957223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:foxtrotgps
Version: 1.2.2-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/foxtrotgps_1.2.2-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
  |   ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from route.c:8:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
 from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
 from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
 from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
 from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
 from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
 from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:33,
 from globals.h:6,
 from hrm_functions.c:19:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is 
deprecated [-Wdeprecated-declarations]
  236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
  | ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from globals.h:6,
 from hrm_functions.c:19:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
  679 | {
  | ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
 from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtk.h:126,
 from globals.h:6,
 from hrm_functions.c:19:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated: 
Use 'GDateTime' instead [-Wdeprecated-declarations]
   73 |   GTimeVal last_popdown;
  |   ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
 from 

Bug#966878: marked as done (figtree: FTBFS: [javac] /<>/src/figtree/application/JSONTreeExporter.java:56: error: JSONTreeExporter is not abstract and does not override abstract method

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 17:18:34 +
with message-id 
and subject line Bug#966878: fixed in figtree 1.4.4-5
has caused the Debian Bug report #966878,
regarding figtree: FTBFS: [javac] 
/<>/src/figtree/application/JSONTreeExporter.java:56: error: 
JSONTreeExporter is not abstract and does not override abstract method close() 
in TreeExporter
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> make: 'build' is up to date.
>  fakeroot debian/rules binary
> dh binary --with javahelper
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>jh_linkjars
>dh_auto_build
>   ant -Duser.name debian
> Buildfile: /<>/build.xml
> 
> init:
>[tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been 
> set to 1575395523
> [mkdir] Created dir: /<>/dist
> 
> compile:
> [javac] /<>/build.xml:40: warning: 'includeantruntime' was 
> not set, defaulting to build.sysclasspath=last; set to false for repeatable 
> builds
> [javac] Compiling 127 source files to /<>/build
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 6
> [javac] warning: [options] source value 6 is obsolete and will be removed 
> in a future release
> [javac] warning: [options] target value 1.6 is obsolete and will be 
> removed in a future release
> [javac] warning: [options] To suppress warnings about obsolete options, 
> use -Xlint:-options.
> [javac] 
> /<>/src/figtree/application/JSONTreeExporter.java:56: error: 
> JSONTreeExporter is not abstract and does not override abstract method 
> close() in TreeExporter
> [javac] public class JSONTreeExporter implements TreeExporter {
> [javac]^
> [javac] 
> /<>/src/figtree/application/JSONTreeExporter.java:181: error: 
> exportTrees(Collection) in JSONTreeExporter cannot implement 
> exportTrees(Collection) in TreeExporter
> [javac] public void exportTrees(Collection trees) 
> throws IOException {
> [javac] ^
> [javac]   overridden method does not throw IOException
> [javac] 
> /<>/src/figtree/application/JSONTreeExporter.java:83: error: 
> exportTree(Tree) in JSONTreeExporter cannot implement exportTree(Tree) in 
> TreeExporter
> [javac] public void exportTree(Tree tree) throws IOException {
> [javac] ^
> [javac]   overridden method does not throw IOException
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 3 errors
> [javac] 4 warnings
> 
> BUILD FAILED
> /<>/build.xml:40: Compile failed; see the compiler error output 
> for details.
> 
> Total time: 2 seconds
> dh_auto_build: error: ant -Duser.name debian returned exit code 1
> make: *** [debian/rules:10: binary] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/figtree_1.4.4-4_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: figtree
Source-Version: 1.4.4-5
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
figtree, 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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated figtree package)

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

Bug#957710: ftbfs with GCC-10

[Antoni Villalonga]

Hi,

I've written a patch.

After that, I've seen Reiner Herrmann already posted a working solution.

It's mostly the same fix but slightly different.
Please consider my version as an alternative. IMAO mine is preferable ;)

Regards,

-- 
Antoni Villalonga
https://friki.cat/
Description: Fix ftbfs with GCC-10
Forwarded: no
Author: Antoni Villalonga 
Last-Update: 2020-08-05
--- a/proxychains/core.h
+++ b/proxychains/core.h
@@ -68,27 +68,27 @@
 
 
 typedef int (*connect_t)(int, const struct sockaddr *, socklen_t);
-connect_t true_connect;
+extern connect_t true_connect;
 
 typedef struct hostent* (*gethostbyname_t)(const char *);
-gethostbyname_t true_gethostbyname;
+extern gethostbyname_t true_gethostbyname;
 
 typedef int (*getaddrinfo_t)(const char *, const char *,
 		const struct addrinfo *,
 		struct addrinfo **);
-getaddrinfo_t true_getaddrinfo;
+extern getaddrinfo_t true_getaddrinfo;
 
 typedef int (*freeaddrinfo_t)(struct addrinfo *);
-freeaddrinfo_t true_freeaddrinfo;
+extern freeaddrinfo_t true_freeaddrinfo;
 
 typedef int (*getnameinfo_t) (const struct sockaddr *,
 		socklen_t, char *,
 		socklen_t, char *,
 		socklen_t, unsigned int);
-getnameinfo_t true_getnameinfo;
+extern getnameinfo_t true_getnameinfo;
 
 typedef struct hostent *(*gethostbyaddr_t) (const void *, socklen_t, int);
-gethostbyaddr_t true_gethostbyaddr;
+extern gethostbyaddr_t true_gethostbyaddr;
 
 int proxy_getaddrinfo(const char *node, const char *service,
 		const struct addrinfo *hints,
--- a/proxychains/libproxychains.c
+++ b/proxychains/libproxychains.c
@@ -81,6 +81,12 @@
 	unsigned int *proxy_count,
 	chain_type *ct,
 	my_network *subnets);
+connect_t true_connect;
+gethostbyname_t true_gethostbyname;
+getaddrinfo_t true_getaddrinfo;
+freeaddrinfo_t true_freeaddrinfo;
+getnameinfo_t true_getnameinfo;
+gethostbyaddr_t true_gethostbyaddr;
 
 static void init_lib()
 {

Bug#967950: doxygen: Autopkgtest regression with json-c 0.15

[Dmitry Shachnev]

Source: doxygen
Version: 1.8.18-1
Severity: serious
Justification: failing autopkgtest on amd64

Dear Maintainer,

doxygen autopkgtest started failing after json-c 0.15-1 was uploaded to
unstable. This blocks migration of some other packages:

https://ci.debian.net/user/britney/jobs?package=doxygen

See any of the “test log” links for the log, for example this one:

https://ci.debian.net/data/autopkgtest/testing/amd64/d/doxygen/6526799/log.gz

The relevant line is:

  error: Doxyfile not found and no input file specified!

Attached is a patch that adapts the test to work with new json-c.

However, I think it would be better if that test did not rely on any external
data, and the needed data was shipped with doxygen itself. Maybe the test can
build doxygen's own documentation?

--
Dmitry Shachnev
diff --git a/debian/tests/control b/debian/tests/control
index f46086a..d707d73 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -1,2 +1,7 @@
 Tests: run
-Depends: apt:native, dpkg-dev, doxygen, graphviz:native
+Depends: apt:native,
+ build-essential,
+ cmake:native,
+ doxygen,
+ dpkg-dev,
+ graphviz:native
diff --git a/debian/tests/run b/debian/tests/run
index 31e4da5..f84a376 100755
--- a/debian/tests/run
+++ b/debian/tests/run
@@ -7,6 +7,10 @@ trap "rm -rf $WORKDIR" 0 INT QUIT ABRT PIPE TERM
 cd $WORKDIR
 apt-get source json-c 2>&1
 cd json-c-*
+mkdir build
+cd build
+cmake ..
+cd doc
 doxygen 2>&1
 cd /
 rm -Rf "$WORKDIR"


signature.asc
Description: PGP signature

Bug#966868: marked as done (igor: FTBFS: CDR3SeqData.h:20:10: error: ‘string’ in namespace ‘std’ does not name a type)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 17:04:08 +
with message-id 
and subject line Bug#966868: fixed in igor 1.4.0+dfsg-2
has caused the Debian Bug report #966868,
regarding igor: FTBFS: CDR3SeqData.h:20:10: error: ‘string’ in namespace ‘std’ 
does not name a type
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.)


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

Hi,

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

Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/jemalloc -I/usr/include/gsl -fopenmp 
> -DIGOR_DATA_DIR=\"/usr/share/igor\" -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o igor-ExtractFeatures.o `test -f 
> 'ExtractFeatures.cpp' || echo './'`ExtractFeatures.cpp
> In file included from ExtractFeatures.h:30,
>  from ExtractFeatures.cpp:26:
> CDR3SeqData.h:20:10: error: ‘string’ in namespace ‘std’ does not name a type
>20 | std::string CDR3nt;
>   |  ^~
> CDR3SeqData.h:1:1: note: ‘std::string’ is defined in header ‘’; did 
> you forget to ‘#include ’?
>   +++ |+#include 
> 1 | 
> CDR3SeqData.h:21:10: error: ‘string’ in namespace ‘std’ does not name a type
>21 | std::string CDR3aa;
>   |  ^~
> CDR3SeqData.h:21:5: note: ‘std::string’ is defined in header ‘’; did 
> you forget to ‘#include ’?
>21 | std::string CDR3aa;
>   | ^~~
> CDR3SeqData.h:22:10: error: ‘string’ in namespace ‘std’ does not name a type
>22 | std::string strData();
>   |  ^~
> CDR3SeqData.h:22:5: note: ‘std::string’ is defined in header ‘’; did 
> you forget to ‘#include ’?
>22 | std::string strData();
>   | ^~~
> g++ -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/jemalloc -I/usr/include/gsl -fopenmp 
> -DIGOR_DATA_DIR=\"/usr/share/igor\" -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o igor-Genechoice.o `test -f 'Genechoice.cpp' || 
> echo './'`Genechoice.cpp
> g++ -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/jemalloc -I/usr/include/gsl -fopenmp 
> -DIGOR_DATA_DIR=\"/usr/share/igor\" -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o igor-GenModel.o `test -f 'GenModel.cpp' || echo 
> './'`GenModel.cpp
> make[3]: *** [Makefile:635: igor-ExtractFeatures.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/igor_1.4.0+dfsg-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: igor
Source-Version: 1.4.0+dfsg-2
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
igor, 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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated igor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Aug 2020 18:37:57 +0200
Source: igor
Architecture: source
Version: 1.4.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 966868
Changes:
 igor (1.4.0+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Fix gcc-10 build
 Closes: #966868
   * debhelper-compat 13 (routine-update)
   * Do not use outdated libcblas any more
Checksums-Sha1:
 abdbef4bfeca05791819c88b5ba38b2772c34260 2046 igor_1.4.0+dfsg-2.dsc
 

Bug#957114: marked as done (ctwm: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 16:03:47 +
with message-id 
and subject line Bug#957114: fixed in ctwm 3.7-5
has caused the Debian Bug report #957114,
regarding ctwm: ftbfs with GCC-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.)


-- 
957114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ctwm
Version: 3.7-4
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/ctwm_3.7-4_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ 
-D_POSIX_C_SOURCE=199309L   -D_POSIX_SOURCE 
-D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE
 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
  -DFUNCPROTO=15 
-DNARROWPROTO-DUSEM4 -DGNOME  -DXPM -DJPEG -DX11R6 -DSOUNDS  -DI18N  
-DUSE_GNU_REGEX  `dpkg-buildflags --get CPPFLAGS`  -c -o workmgr.o workmgr.c
In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
 from /usr/include/stdio.h:27,
 from workmgr.c:26:
/usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
_DEFAULT_SOURCE"
  |   ^~~
gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ 
-D_POSIX_C_SOURCE=199309L   -D_POSIX_SOURCE 
-D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE
 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
  -DFUNCPROTO=15 
-DNARROWPROTO-DUSEM4 -DGNOME  -DXPM -DJPEG -DX11R6 -DSOUNDS  -DI18N  
-DUSE_GNU_REGEX  `dpkg-buildflags --get CPPFLAGS`  -c -o windowbox.o windowbox.c
In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
 from /usr/include/stdio.h:27,
 from windowbox.c:28:
/usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
_DEFAULT_SOURCE"
  |   ^~~
gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ 
-D_POSIX_C_SOURCE=199309L   -D_POSIX_SOURCE 
-D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE
 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
  -DFUNCPROTO=15 
-DNARROWPROTO-DUSEM4 -DGNOME  -DXPM -DJPEG -DX11R6 -DSOUNDS  -DI18N  
-DUSE_GNU_REGEX  `dpkg-buildflags --get CPPFLAGS`  -c -o clicktofocus.o 
clicktofocus.c
In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
 from /usr/include/X11/Xlib.h:38,
 from twm.h:81,
 from clicktofocus.h:4,
 from clicktofocus.c:1:
/usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
_DEFAULT_SOURCE"
  |   ^~~
gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ 
-D_POSIX_C_SOURCE=199309L 

Bug#957620: marked as done (nvtv: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 16:05:42 +
with message-id 
and subject line Bug#957620: fixed in nvtv 0.4.7-8.1
has caused the Debian Bug report #957620,
regarding nvtv: ftbfs with GCC-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.)


-- 
957620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nvtv
Version: 0.4.7-8
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/nvtv_0.4.7-8_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from gui_i810.c:28:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
  679 | {
  | ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
 from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtk.h:126,
 from gui_i810.c:28:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated: 
Use 'GDateTime' instead [-Wdeprecated-declarations]
   73 |   GTimeVal last_popdown;
  |   ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from gui_i810.c:28:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
gcc  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/fribidi -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16  -Wl,-z,relro 
-Wl,-dy,--as-needed -o nvtv nvtv.o print.o libc_wrapper.o xf86i2c.o pipe.o 
mmio.o tv_common.o tv_nv.o tv_tdfx.o tv_i810.o tv_i2c.o tv_null.o tv_bt.o 
tv_cx.o tv_nx.o tv_ch1_7007.o tv_ch2_7009.o tv_ph1_saa7102.o tv_ph2_saa7104.o 
data.o data_bt.o data_cx.o data_ch.o data_ph.o data_nx.o data_nv.o data_tdfx.o 
data_i810.o data_xbox.o data_vesa.o calc_bt.o back_direct.o back_nvidia.o 
back_tdfx.o ba
 ck_i810.o back_null.o card_direct.o back_unix.o back_client.o actions.o gui.o 
gui_bt.o gui_cx.o gui_ch.o gui_ph.o gui_nx.o gui_nv.o gui_tdfx.o gui_i810.o 
-lSM -lICE   -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo 
-lgdk_pixbuf-2.0 

Bug#966692: stunnel4: FTBFS because of test hang

[Peter Pentchev]

On Wed, Aug 05, 2020 at 10:52:31PM +0200, Michał Mirosław wrote:
> On Wed, Aug 05, 2020 at 09:28:12PM +0300, Peter Pentchev wrote:
> > On Wed, Aug 05, 2020 at 08:01:53PM +0200, Michał Mirosław wrote:
> > > On Sun, Aug 02, 2020 at 05:34:40PM +0300, Peter Pentchev wrote:
> > > > On Sun, Aug 02, 2020 at 02:02:22AM +0200, Michał Mirosław wrote:
> > > [...]
> > > > --- a/debian/tests/runtime
> > > > +++ b/debian/tests/runtime
> > > > @@ -432,6 +432,7 @@ MAIN:
> > > >  
> > > > if (!defined $line) {
> > > > $eof->send($got_version);
> > > > +   undef $f_out;
> > > > } elsif (!$got_version) {
> > > > if ($line =~ m{^
> > > > stunnel \s+
> > > 
> > > I believe $f_out will not be defined here, as it only gets set after
> > > sub{} is created. Perl confirms this:
> > > 
> > > $ TEST_STUNNEL=src/stunnel strace -f -o /tmp/log debian/tests/runtime
> > > Global symbol "$f_out" requires explicit package name (did you forget to 
> > > declare "my $f_out"?) at debian/tests/runtime line 435.
> > > Execution of debian/tests/runtime aborted due to compilation errors.
> > 
> > Of course you're right. Sorry about that! That's what I get for writing
> > a patch three minutes before I have to head out and never remembering to
> > actually test it later :(
> > 
> > How about the attached one?
[snip]
> 
> This stops the endless readings of EOF, but:
> 
> 1. the FD gets leaked (shouldn't matter much, though)
> 2. the test hangs anyway
> 
> Using print-debugging, I see that it stops at wait_for_child line just
> after printing the version. It seems that something is reaping the child
> before the main thread has a chance to wait for it.

OK, so the only thing that comes to my mind now is that you may be
hitting a crazy, crazy race between register_child() and child_reaper(),
and I say "a crazy, crazy race", because the test has to (apparently
reproducibly) receive the CHLD signal exactly between the check and
the creation in register_child()'s first "$children{...} //= ...cv"
statement.

Can you apply the following patch and show me the output of running
the test?

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#967199: marked as done (pypy: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 5 Aug 2020 17:35:39 +
with message-id <20200805173539.3rjkikitsvx4f...@satie.tumbleweed.org.za>
and subject line Re: Bug#967199: pypy: Unversioned Python removal in 
sid/bullseye
has caused the Debian Bug report #967199,
regarding pypy: Unversioned Python 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.)


-- 
967199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pypy
Version: 7.3.1+dfsg-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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 ---
Hi Matthias (2020.08.04_09:29:04_+)
> Your package either build-depends, depends on one of those packages.

Nope, it doesn't. It remains buildable and installable, so don't think
there's any action to take here.

There was #967036, but that's fixed.

SR

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

Bug#967201: marked as done (pypy3: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 5 Aug 2020 17:35:57 +
with message-id <20200805173556.yamlnsd73sqbn...@satie.tumbleweed.org.za>
and subject line Re: Bug#967201: pypy3: Unversioned Python removal in 
sid/bullseye
has caused the Debian Bug report #967201,
regarding pypy3: Unversioned Python 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.)


-- 
967201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pypy3
Version: 7.3.1+dfsg-4
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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 ---
Hi Matthias (2020.08.04_09:29:03_+)
> Your package either build-depends, depends on one of those packages.

Nope, it doesn't. It remains buildable and installable, so don't think
there's any action to take here.

There was #967036, but that's fixed.

SR

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

Bug#936873: libhdate: diff for NMU version 1.6.02-2.1

[Moritz Mühlenhoff]

The debdiff for my NMU for libhdate (versioned as 1.6.02-2.1)

Cheers,
Moritz
diff -Nru libhdate-1.6.02/debian/changelog libhdate-1.6.02/debian/changelog
--- libhdate-1.6.02/debian/changelog	2018-07-30 05:49:11.0 +0200
+++ libhdate-1.6.02/debian/changelog	2020-08-02 23:13:33.0 +0200
@@ -1,3 +1,11 @@
+libhdate (1.6.02-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python-hdate, there are no remaining rdeps remaining
+(Closes: #936873)
+
+ -- Moritz Muehlenhoff   Sun, 02 Aug 2020 23:13:33 +0200
+
 libhdate (1.6.02-2) unstable; urgency=medium
 
   * Update maintainer address (Closes: #899576)
diff -Nru libhdate-1.6.02/debian/control libhdate-1.6.02/debian/control
--- libhdate-1.6.02/debian/control	2018-07-30 05:41:00.0 +0200
+++ libhdate-1.6.02/debian/control	2020-08-02 23:11:28.0 +0200
@@ -7,8 +7,6 @@
 Vcs-Git: https://salsa.debian.org/hebrew-team/libhdate.git
 Build-Depends: debhelper (>= 9),
  swig,
- python-dev (>= 2.6.6-3~),
- dh-python,
  dh-autoreconf,
 Standards-Version: 3.9.8
 Homepage: http://libhdate.sourceforge.net/
@@ -26,20 +24,6 @@
  This package contains headers and support files required
  to build new applications with libhdate.
 
-Package: python-hdate
-Section: python
-Architecture: any
-Provides: ${python:Provides}
-Depends: libhdate1 (= ${binary:Version}), ${python:Depends}, ${shlibs:Depends}, ${misc:Depends}
-Description: Provides a library that help use Hebrew dates (Python bindings)
- LibHdate is a small C,C++ library for Hebrew dates,
- holidays, and reading sequence (parasha). It is using 
- the source code from Amos Shapir's "hdate" package fixed and 
- patched by Nadav Har'El. The Torah reading sequence
- is from tables by Zvi Har'El.
- .
- This package contains Python bindings to libhdate
-
 Package: libhdate-perl
 Section: perl
 Architecture: any
diff -Nru libhdate-1.6.02/debian/python-hdate.install libhdate-1.6.02/debian/python-hdate.install
--- libhdate-1.6.02/debian/python-hdate.install	2018-07-30 05:28:32.0 +0200
+++ libhdate-1.6.02/debian/python-hdate.install	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-usr/lib/python*/*
diff -Nru libhdate-1.6.02/debian/rules libhdate-1.6.02/debian/rules
--- libhdate-1.6.02/debian/rules	2018-07-30 05:28:32.0 +0200
+++ libhdate-1.6.02/debian/rules	2020-08-02 23:11:45.0 +0200
@@ -3,10 +3,7 @@
 ARCHLIB := $(shell perl -MConfig -e 'print $$Config{vendorarch}')
 
 %:
-	dh $* --with python2,autoreconf
+	dh $* --with autoreconf
 
 override_dh_auto_configure:
 	dh_auto_configure -- --with-perl-sitelib-dir=$(ARCHLIB)
-
-override_dh_python2:
-	dh_python2 -s --no-guessing-versions

Bug#966692: stunnel4: FTBFS because of test hang

[Michał Mirosław]

On Sun, Aug 02, 2020 at 05:34:40PM +0300, Peter Pentchev wrote:
> On Sun, Aug 02, 2020 at 02:02:22AM +0200, Michał Mirosław wrote:
[...]
> --- a/debian/tests/runtime
> +++ b/debian/tests/runtime
> @@ -432,6 +432,7 @@ MAIN:
>  
>   if (!defined $line) {
>   $eof->send($got_version);
> + undef $f_out;
>   } elsif (!$got_version) {
>   if ($line =~ m{^
>   stunnel \s+

I believe $f_out will not be defined here, as it only gets set after
sub{} is created. Perl confirms this:

$ TEST_STUNNEL=src/stunnel strace -f -o /tmp/log debian/tests/runtime
Global symbol "$f_out" requires explicit package name (did you forget to 
declare "my $f_out"?) at debian/tests/runtime line 435.
Execution of debian/tests/runtime aborted due to compilation errors.

$ dpkg -l perl
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  perl   5.28.1-6 amd64Larry Wall's Practical Extraction 
and Report Language

Best Regards
Michał Mirosław

Bug#957360: insighttoolkit4: ftbfs with GCC-10

[Étienne Mollier]

Greetings,

Étienne Mollier, on 2020-08-04 20:31:23 +0200:
> On Mon, 3 Aug 2020 08:45:35 +0200 Étienne Mollier 
>  wrote:
> >   * an update to ITK 4.13.3.
> 
> I am now working on this part.  Hopefuly this will help getting
> through the build process further.

I updated the package to version 4.13.3, and so, last night
build went through; actually it ended around 11:00 AM today.
I'm seeing several test failures in the build log, with a
message like:

ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
preloaded (cannot open shared object file): ignored.
Loading ITKPyBase... Traceback (most recent call last):
  File "", line 1, in 
  File 
"/home/emollier/debian/med-team/insighttoolkit/BUILD/Wrapping/Generators/Python/itkLazy.py",
 line 44, in __getattribute__
itkBase.LoadModule(module, namespace)
  File 
"/home/emollier/debian/med-team/insighttoolkit/BUILD/Wrapping/Generators/Python/itkBase.py",
 line 118, in LoadModule
LoadModule(dep, namespace)
  File 
"/home/emollier/debian/med-team/insighttoolkit/BUILD/Wrapping/Generators/Python/itkBase.py",
 line 118, in LoadModule
LoadModule(dep, namespace)
  File 
"/home/emollier/debian/med-team/insighttoolkit/BUILD/Wrapping/Generators/Python/itkBase.py",
 line 128, in LoadModule
module = loader.load(swigModuleName)
  File 
"/home/emollier/debian/med-team/insighttoolkit/BUILD/Wrapping/Generators/Python/itkBase.py",
 line 250, in load
return imp.load_module(name, fp, pathname, description)
  File 
"/home/emollier/debian/med-team/insighttoolkit/BUILD/lib/ITKPyBasePython.py", 
line 15, in 
import _ITKPyBasePython
ImportError: 
/home/emollier/debian/med-team/insighttoolkit/BUILD/lib/_ITKPyBasePython.so: 
undefined symbol: PyUnicode_FromFormat

However, I am suspecting an ill placed `fakeroot` in my building
command.  That may just be my bad hopefully.  I will redo a run
in a clean chroot.

Kind Regards,
-- 
Étienne Mollier 
Old rsa/3072: 5ab1 4edf 63bb ccff 8b54  2fa9 59da 56fe fff3 882d
New rsa/4096: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/1, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#966562: marked as done (altos: hardcodes runtime json-c dependency)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 18:18:31 +
with message-id 
and subject line Bug#966562: fixed in altos 1.9.4-2
has caused the Debian Bug report #966562,
regarding altos: hardcodes runtime json-c dependency
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.)


-- 
966562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: altos
Version: 1.9.4-1
Severity: serious
tags: patch

Hello, please update to -c5 or better drop it

in case you want to keep it,

sed s/libjson-c4/libjson-c5/g -i debian/control does the job

G.
--- End Message ---
--- Begin Message ---
Source: altos
Source-Version: 1.9.4-2
Done: Bdale Garbee 

We believe that the bug you reported is fixed in the latest version of
altos, 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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bdale Garbee  (supplier of updated altos package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Aug 2020 11:27:40 -0600
Source: altos
Architecture: source
Version: 1.9.4-2
Distribution: unstable
Urgency: medium
Maintainer: Bdale Garbee 
Changed-By: Bdale Garbee 
Closes: 966562
Changes:
 altos (1.9.4-2) unstable; urgency=medium
 .
   * eliminate old explicit run-time dep on libjson-c4, closes: #966562
Checksums-Sha1:
 28f9d52a9ee669489d74c23d8ec3453a13b47aa6 2263 altos_1.9.4-2.dsc
 b26ee95c2fc2a8dc81582a352af6e6733e39bdb5 77556 altos_1.9.4-2.debian.tar.xz
 bb3bced5bfbba3d6bd0b1820a8a50090b21e9c1c 12033 altos_1.9.4-2_amd64.buildinfo
Checksums-Sha256:
 d4d4a34c8ceec850fe176ffdbd0b09b70556991ecfcfe3322c331208a510bf19 2263 
altos_1.9.4-2.dsc
 09b3924c9b6b73c33049246fdb8528271e257061fc9bdb23dea938745d7bdaf0 77556 
altos_1.9.4-2.debian.tar.xz
 38942fe7334934df8de6e15f4ff22cce165b7334362660512279526f027d373a 12033 
altos_1.9.4-2_amd64.buildinfo
Files:
 8b3dff8a8dd9fc804953d512c847c27f 2263 electronics optional altos_1.9.4-2.dsc
 cd479ca840a9edcaade2f7194b26a777 77556 electronics optional 
altos_1.9.4-2.debian.tar.xz
 662b95f79322d6ffce85f9329f43d573 12033 electronics optional 
altos_1.9.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEHguq2FwiMqGzzpLrtwRxBYMLn6EFAl8q8mcACgkQtwRxBYML
n6GIfg/+MfsEqZDKfinGDjs1En8e1bB91QYMYC56j9D1eoqM0dQiMf9p9LOhFOJ/
iBvuDPsM3A1HHZVDc1miOlDb+WM26JbrL9cEx0P+tett3MgnQ/TyqovfJj9nQ88z
ncSIyl6EWqf7JkrPbcQ1zK4DkGeV8eWG0ny8YPL7l9aPrn+U4a19msucvS5yYD1m
wqM3/t09ZNkWa3rHL3E5bh0aoBm/ZNa/QgcG55eRtowF9TK2jdvBJf2MykxCAQD4
YJUDtrU7VZZObJXQNg4Xd4X+HVVHDDK7bHJuNvCUXj9/A2eltTYDjfxj5y2geJdX
wqidZE0UdU/7QU+D0LN2dH6jlmQd3jUhi95TW3+3mGLgJlxRYFhyebx1Ek72c5/F
3CXabWSH4CMm0VQlOX4MvECckE87EnThjQrTD8c5gJKU+3CK4W1tmmNrQQXRf/9C
KJdSK9Dpa6H4w+hM8kwvv/OmKfdaCXN7B8UqKhV9V1Q7ZQh3oBckWkpFaAinRXnr
4G4+pu9/X2WVa9MDL/xKJA3a/ufYg6qWZQnDN6afjjqEtdeN1Jhrk9K7U5dsXGm4
ALcfPQx9JLHkQagno7zmpa0nD9oGgWkww4n061AuOj0Mf8B7ANaV97mFmJsSY6S/
jztkp2bM8ByfpgPgkORmq6DX/wgmsQywktOvr5Zei5zhFNsAgN8=
=V+Os
-END PGP SIGNATURE End Message ---

Bug#957019: atlc: diff for NMU version 4.6.1-2.1

[Bdale Garbee]

Sudip Mukherjee  writes:

> Control: tags 957019 + patch
> Control: tags 957019 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for atlc (versioned as 4.6.1-2.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should cancel it.

Thank you!

Bdale


signature.asc
Description: PGP signature

Bug#967953: Package not installable in sid due to missing dependencies python-argcomplete and python-ipaddr

[Julian Brost]

Package: ifupdown2
Version: 1.2.7-1
Severity: grave

The package ifupdown2 currently cannot be installed on systems running 
sid as the two of its dependencies, python-argcomplete and 
python-ipaddr, are no longer present in sid.


The suggested packages python-gvgen and python-mako also no longer exist.

Bug#966692: stunnel4: FTBFS because of test hang

[Peter Pentchev]

On Wed, Aug 05, 2020 at 08:01:53PM +0200, Michał Mirosław wrote:
> On Sun, Aug 02, 2020 at 05:34:40PM +0300, Peter Pentchev wrote:
> > On Sun, Aug 02, 2020 at 02:02:22AM +0200, Michał Mirosław wrote:
> [...]
> > --- a/debian/tests/runtime
> > +++ b/debian/tests/runtime
> > @@ -432,6 +432,7 @@ MAIN:
> >  
> > if (!defined $line) {
> > $eof->send($got_version);
> > +   undef $f_out;
> > } elsif (!$got_version) {
> > if ($line =~ m{^
> > stunnel \s+
> 
> I believe $f_out will not be defined here, as it only gets set after
> sub{} is created. Perl confirms this:
> 
> $ TEST_STUNNEL=src/stunnel strace -f -o /tmp/log debian/tests/runtime
> Global symbol "$f_out" requires explicit package name (did you forget to 
> declare "my $f_out"?) at debian/tests/runtime line 435.
> Execution of debian/tests/runtime aborted due to compilation errors.

Of course you're right. Sorry about that! That's what I get for writing
a patch three minutes before I have to head out and never remembering to
actually test it later :(

How about the attached one?

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13
commit eb303ad2e9c925bf7243e6877d8598d0356d68f9
Author: Peter Pentchev 
Date:   Sun Aug 2 17:31:26 2020 +0300

Destroy the stunnel version watcher on EOF.

diff --git a/debian/tests/runtime b/debian/tests/runtime
index ecffe7b..f594d9a 100755
--- a/debian/tests/runtime
+++ b/debian/tests/runtime
@@ -424,7 +424,8 @@ MAIN:
 
my ($got_version, $before_version) = (undef, '');
my $eof = AnyEvent->condvar;
-   my $f_out = AnyEvent->io(
+   my $f_out;
+   $f_out = AnyEvent->io(
fh => $s_in,
poll => 'r',
cb => sub {
@@ -432,6 +433,7 @@ MAIN:
 
if (!defined $line) {
$eof->send($got_version);
+   undef $f_out;
} elsif (!$got_version) {
if ($line =~ m{^
stunnel \s+


signature.asc
Description: PGP signature

Bug#936873: libhdate: diff for NMU version 1.6.02-2.1

[Boruch Baum]

Thanks Moritz for stepping forward and adopting this. I still haven't
heard back from any member of the 'Debian Hebrew Maintainers' team, but
will continue in the future to attempt to use them as a first point of
contact until/unless I hear that they have been disolved / superseded /
replaced. Any word on why the silence from them?

On 2020-08-05 19:57, Moritz Mühlenhoff wrote:
> The debdiff for my NMU for libhdate (versioned as 1.6.02-2.1)
>
> Cheers,
> Moritz

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0

Bug#967956: golang-github-unknwon-cae: CVE-2020-7668

[Salvatore Bonaccorso]

Source: golang-github-unknwon-cae
Version: 0.0~git20160715.0.c6aac99-4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for golang-github-unknwon-cae.

CVE-2020-7668[0]:
| In all versions of the package github.com/unknwon/cae/tz, the
| ExtractTo function doesn't securely escape file paths in zip archives
| which include leading or non-leading "..". This allows an attacker to
| add or replace files system-wide.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-7668
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7668

Regards,
Salvatore

Bug#967955: golang-github-unknwon-cae: CVE-2020-7664

[Salvatore Bonaccorso]

Source: golang-github-unknwon-cae
Version: 0.0~git20160715.0.c6aac99-4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for golang-github-unknwon-cae.

CVE-2020-7664[0]:
| In all versions of the package github.com/unknwon/cae/zip, the
| ExtractTo function doesn't securely escape file paths in zip archives
| which include leading or non-leading "..". This allows an attacker to
| add or replace files system-wide.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-7664
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7664
[1] https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMUNKNWONCAEZIP-570383

Regards,
Salvatore

Bug#957368: marked as done (ipip: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 20:35:30 +
with message-id 
and subject line Bug#957368: fixed in ipip 1.1.10
has caused the Debian Bug report #957368,
regarding ipip: ftbfs with GCC-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.)


-- 
957368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ipip
Version: 1.1.9
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/ipip_1.1.9_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
  | ^~~~
main.c: In function ‘main’:
main.c:45:9: warning: variable ‘now’ set but not used 
[-Wunused-but-set-variable]
   45 |  time_t now;
  | ^~~
gcc -DLINUX -DUSE_TERMIOS -g -O2 -Wall  -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
route.o route.c
gcc -DLINUX -DUSE_TERMIOS -g -O2 -Wall  -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
run.o run.c
gcc -DLINUX -DUSE_TERMIOS -g -O2 -Wall  -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
slip.o slip.c
gcc -DLINUX -DUSE_TERMIOS -g -O2 -Wall  -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
tun.o tun.c
gcc -Wl,-z,relro -DLINUX -DUSE_TERMIOS -g -O2 -Wall  -o ipip config.o ip.o 
main.o route.o run.o slip.o tun.o
/usr/bin/ld: ip.o:/<>/ipip.h:53: multiple definition of 
`progname'; config.o:/<>/ipip.h:53: first defined here
/usr/bin/ld: ip.o:/<>/ipip.h:132: multiple definition of 
`ifs_top'; config.o:/<>/ipip.h:132: first defined here
/usr/bin/ld: ip.o:/<>/ipip.h:131: multiple definition of `ifs'; 
config.o:/<>/ipip.h:131: first defined here
/usr/bin/ld: ip.o:/<>/ipip.h:129: multiple definition of 
`rts_top'; config.o:/<>/ipip.h:129: first defined here
/usr/bin/ld: ip.o:/<>/ipip.h:125: multiple definition of `rts'; 
config.o:/<>/ipip.h:125: first defined here
/usr/bin/ld: ip.o:/<>/ipip.h:55: multiple definition of 
`stat_interval'; config.o:/<>/ipip.h:55: first defined here
/usr/bin/ld: ip.o:/<>/ipip.h:54: multiple definition of 
`no_timestamp'; config.o:/<>/ipip.h:54: first defined here
/usr/bin/ld: ip.o:/<>/ipip.h:52: multiple definition of `debugt'; 
config.o:/<>/ipip.h:52: first defined here
/usr/bin/ld: ip.o:/<>/ipip.h:51: multiple definition of `debugd'; 
config.o:/<>/ipip.h:51: first defined here
/usr/bin/ld: main.o:/<>/ipip.h:51: multiple definition of 
`debugd'; config.o:/<>/ipip.h:51: first defined here
/usr/bin/ld: main.o:/<>/ipip.h:52: multiple definition of 
`debugt'; config.o:/<>/ipip.h:52: first defined here
/usr/bin/ld: main.o:/<>/ipip.h:54: multiple definition of 
`no_timestamp'; config.o:/<>/ipip.h:54: first defined here
/usr/bin/ld: main.o:/<>/ipip.h:55: multiple definition of 
`stat_interval'; config.o:/<>/ipip.h:55: first defined here
/usr/bin/ld: main.o:/<>/ipip.h:53: multiple definition of 
`progname'; config.o:/<>/ipip.h:53: first defined here
/usr/bin/ld: main.o:/<>/ipip.h:132: multiple definition of 
`ifs_top'; config.o:/<>/ipip.h:132: first defined here
/usr/bin/ld: main.o:/<>/ipip.h:131: multiple definition of `ifs'; 
config.o:/<>/ipip.h:131: first defined here
/usr/bin/ld: main.o:/<>/ipip.h:129: multiple definition of 
`rts_top'; config.o:/<>/ipip.h:129: first defined here
/usr/bin/ld: main.o:/<>/ipip.h:125: multiple definition of `rts'; 
config.o:/<>/ipip.h:125: first defined here
/usr/bin/ld: route.o:/<>/ipip.h:129: multiple definition of 
`rts_top'; config.o:/<>/ipip.h:129: first defined here
/usr/bin/ld: route.o:/<>/ipip.h:125: multiple definition of `rts'; 
config.o:/<>/ipip.h:125: first defined here
/usr/bin/ld: 

Bug#964679: marked as done (gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2020 20:35:25 +
with message-id 
and subject line Bug#964679: fixed in gtk+3.0 3.24.21-1
has caused the Debian Bug report #964679,
regarding gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in 
the symbols file: see diff output below
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.)


-- 
964679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtk+3.0
Version: 3.24.20-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_makeshlibs -plibgtk-3-0 --add-udeb=libgtk-3-0-udeb 
> -Xusr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0 -- -c4
> dpkg-gensymbols: error: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: warning: debian/libgtk-3-0/DEBIAN/symbols doesn't match 
> completely debian/libgtk-3-0.symbols
> --- debian/libgtk-3-0.symbols (libgtk-3-0_3.24.20-1_amd64)
> +++ dpkg-gensymbolseXFnOd 2020-07-09 00:50:15.027590197 +
> @@ -1,5 +1,8 @@
>  libgdk-3.so.0 libgtk-3-0 #MINVER#
>  * Build-Depends-Package: libgtk-3-dev
> + _gdk_get_resource@Base 3.24.20-1
> + _gdk_register_resource@Base 3.24.20-1
> + _gdk_unregister_resource@Base 3.24.20-1
>   gdk__private__@Base 3.16.2
>   gdk_add_option_entries_libgtk_only@Base 3.0.0
>   gdk_anchor_hints_get_type@Base 3.21.5
> @@ -758,6 +761,9 @@
>   gdk_x11_xatom_to_atom@Base 3.0.0
>   gdk_x11_xatom_to_atom_for_display@Base 3.0.0
>  libgtk-3.so.0 libgtk-3-0 #MINVER#
> + _gtk_get_resource@Base 3.24.20-1
> + _gtk_register_resource@Base 3.24.20-1
> + _gtk_unregister_resource@Base 3.24.20-1
>   gtk_about_dialog_add_credit_section@Base 3.3.16
>   gtk_about_dialog_get_artists@Base 3.0.0
>   gtk_about_dialog_get_authors@Base 3.0.0
> dh_makeshlibs: error: failing due to earlier errors
> make[1]: *** [debian/rules:240: override_dh_makeshlibs] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/gtk+3.0_3.24.20-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: gtk+3.0
Source-Version: 3.24.21-1
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
gtk+3.0, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gtk+3.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Aug 2020 15:33:48 +0100
Source: gtk+3.0
Architecture: source
Version: 3.24.21-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 960303 964679
Changes:
 gtk+3.0 (3.24.21-1) experimental; urgency=medium
 .
   * Team upload
   * New upstream release
 - Fix ability to use BSD-3-clause, Apache 2.0 and MPL 2.0 in
   GtkAboutDialog (Closes: #960303)
   * Add patch to fix FTBFS with newer GLib versions (Closes: #964679)
Checksums-Sha1:
 65270af3ce100a3475975542e5ca48fe2923f3c2 3945 gtk+3.0_3.24.21-1.dsc
 c34360a46556732d0143b2fd010f4065e9c3987b 21353740 gtk+3.0_3.24.21.orig.tar.xz
 25cc4db5aab2a67d50c93b1316527b59fc35a9a7 156680 gtk+3.0_3.24.21-1.debian.tar.xz
 a60b8de0be25386bd5c56748d5871ef6dffda500 14609 
gtk+3.0_3.24.21-1_source.buildinfo
Checksums-Sha256:
 98abfd82fa8333c4b23c76f1ff3cbfd51dc6fd55ae5b3e9ccc84bff2d89e28c1 3945 
gtk+3.0_3.24.21-1.dsc
 aeea6ae7cd35e83dfc7699be716519faefca346c62e784dd1a37d9df94c08f52 21353740 
gtk+3.0_3.24.21.orig.tar.xz
 259df6378bde53a78fdedc3d1b1f4472233b49c4a7f5880f4c16e1dd1bfe03b3 156680 
gtk+3.0_3.24.21-1.debian.tar.xz