Bug#972239: geoalchemy2 build-depends on obsolete packages.

[peter green]

Package: geoalchemy2
Version: 0.7.0-1
Severity: serious

geoalchemy2 build-depends on postgresql-12-postgis-3 and 
postgresql-12-postgis-3-scripts,
which have been replaced by postgresql-13-postgis-3 
postgresql-13-postgis-3-scripts, the
old packages are still present in unstable as cruft packages, but are 
completely gone from
testing.

This issue affects both versions 0.7.0-1 (in testing) and 0.8.4-2 (in unstable).

Processed: affects 971995

[Debian Bug Tracking System]

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

> affects 971995 src:python-eventlet
Bug #971995 [src:python-greenlet] python-greenlet ftbfs with python3-defaults 
(python3.9) from experimental
Bug #972025 [src:python-greenlet] python-greenlet ftbfs with python3.9 as 
supported python version
Added indication that 971995 affects src:python-eventlet
Added indication that 972025 affects src:python-eventlet
> thanks
Stopping processing here.

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

Bug#972238: read-edid FTBFS with gcc-10

[Helmut Grohne]

Source: read-edid
Version: 3.0.2-1
Severity: serious
Tags: ftbfs

read-edid fails to build from source in unstable due to -fno-commons
having become default in gcc-10. Here is a sample output:

| cd /<>/obj-s390x-linux-gnu/get-edid && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/get-edid.dir/link.txt --verbose=1
| /usr/bin/s390x-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -rdynamic CMakeFiles/get-edid.dir/get-edid.c.o 
CMakeFiles/get-edid.dir/classic.c.o CMakeFiles/get-edid.dir/i2c.c.o -o get-edid
| /usr/lib/gcc-cross/s390x-linux-gnu/10/../../../../s390x-linux-gnu/bin/ld: 
CMakeFiles/get-edid.dir/i2c.c.o:./obj-s390x-linux-gnu/get-edid/./get-edid/i2c.c:18:
 multiple definition of `quiet'; 
CMakeFiles/get-edid.dir/get-edid.c.o:./obj-s390x-linux-gnu/get-edid/./get-edid/get-edid.c:12:
 first defined here
| collect2: error: ld returned 1 exit status
| make[3]: *** [get-edid/CMakeFiles/get-edid.dir/build.make:136: 
get-edid/get-edid] Error 1
| make[3]: Leaving directory '/<>/obj-s390x-linux-gnu'
| make[2]: *** [CMakeFiles/Makefile2:137: get-edid/CMakeFiles/get-edid.dir/all] 
Error 2
| make[2]: Leaving directory '/<>/obj-s390x-linux-gnu'
| make[1]: *** [Makefile:152: all] Error 2
| make[1]: Leaving directory '/<>/obj-s390x-linux-gnu'
| dh_auto_build: error: cd obj-s390x-linux-gnu && make -j1 returned exit code 2
| make: *** [debian/rules:11: build-arch] Error 25
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Helmut

Processed: libopenmpi3: mca_pmix_pmix3x.so is still shipped on armel/mipsel

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:med-fichier
Bug #972236 [libopenmpi3] libopenmpi3: mca_pmix_pmix3x.so is still shipped on 
armel/mipsel
Added indication that 972236 affects src:med-fichier

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

Bug#972236: libopenmpi3: mca_pmix_pmix3x.so is still shipped on armel/mipsel

[Adrian Bunk]

Package: libopenmpi3
Version: 4.0.5-6
Severity: serious
Tags: ftbfs
Control: affects -1 src:med-fichier

openmpi (4.0.5-6) unstable; urgency=medium
...
  * Rebuild to drop build of mca_pmix_pmix3.so on armel/mipsel (triggered by
misconfig in pmix package) ?
...


Seems this didn't work:
libopenmpi3:armel: 
/usr/lib/arm-linux-gnueabi/openmpi/lib/openmpi3/mca_pmix_pmix3x.so

https://buildd.debian.org/status/logs.php?pkg=med-fichier=4.1.0%2Brepack-2%2Bb1

...
[mipsel-manda-05:09103] mca_base_component_repository_open: unable to open 
mca_pmix_pmix3x: 
/usr/lib/mipsel-linux-gnu/openmpi/lib/openmpi3/mca_pmix_pmix3x.so: undefined 
symbol: OPAL_MCA_PMIX3X_PMIx_Get_version (ignored)
...


Could armel and mipsel be removed from NO_PMIX_ARCH now that
#970194 is fixed?

Bug#971099: rust-sequoia-openpgp: FTBFS: unsatisfiable build-dependencies: librust-dyn-clone-1+default-dev but it is not installable

[Daniel Kahn Gillmor]

On Sun 2020-09-27 20:38:38 +0200, Lucas Nussbaum wrote:
> Source: rust-sequoia-openpgp
> Version: 0.18.0-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200926 ftbfs-bullseye

rust-dyn-clone made it out of NEW on 2020-10-09, so rust-sequoia-openpgp
0.18.0-2 is now building just fine on the buildd network.

 --dkg


signature.asc
Description: PGP signature

Bug#971099: marked as done (rust-sequoia-openpgp: FTBFS: unsatisfiable build-dependencies: librust-dyn-clone-1+default-dev but it is not installable)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 23:12:52 -0400
with message-id <87imbcw5aj@fifthhorseman.net>
and subject line Re: Bug#971099: rust-sequoia-openpgp: FTBFS: unsatisfiable 
build-dependencies: librust-dyn-clone-1+default-dev but it is not installable
has caused the Debian Bug report #971099,
regarding rust-sequoia-openpgp: FTBFS: unsatisfiable build-dependencies: 
librust-dyn-clone-1+default-dev but it is not installable
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.)


-- 
971099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-sequoia-openpgp
Version: 0.18.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, 
> libstd-rust-dev, librust-anyhow-1+default-dev, 
> librust-backtrace-0.3+default-dev, librust-base64-0.12+default-dev | 
> librust-base64-0.11+default-dev, 
> librust-buffered-reader-0.18+compression-bzip2-dev, 
> librust-buffered-reader-0.18+compression-deflate-dev, 
> librust-buffered-reader-0.18-dev, librust-bzip2-0.3+default-dev (>= 
> 0.3.2-~~), librust-dyn-clone-1+default-dev, librust-flate2-1+default-dev (>= 
> 1.0.1-~~), librust-idna-0.2+default-dev, librust-lalrpop-0.17+default-dev, 
> librust-lalrpop-util-0.17+default-dev, librust-lazy-static-1+default-dev (>= 
> 1.3-~~), librust-libc-0.2+default-dev, librust-memsec-0.5+default-dev (>= 
> 0.5.6-~~), librust-nettle-7+default-dev, librust-regex-1+default-dev, 
> librust-thiserror-1+default-dev, 
> librust-unicode-normalization-0.1+default-dev (>= 0.1.9-~~), build-essential, 
> fakeroot
> Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, 
> libstd-rust-dev, librust-anyhow-1+default-dev, 
> librust-backtrace-0.3+default-dev, librust-base64-0.12+default-dev, 
> librust-buffered-reader-0.18+compression-bzip2-dev, 
> librust-buffered-reader-0.18+compression-deflate-dev, 
> librust-buffered-reader-0.18-dev, librust-bzip2-0.3+default-dev (>= 
> 0.3.2-~~), librust-dyn-clone-1+default-dev, librust-flate2-1+default-dev (>= 
> 1.0.1-~~), librust-idna-0.2+default-dev, librust-lalrpop-0.17+default-dev, 
> librust-lalrpop-util-0.17+default-dev, librust-lazy-static-1+default-dev (>= 
> 1.3-~~), librust-libc-0.2+default-dev, librust-memsec-0.5+default-dev (>= 
> 0.5.6-~~), librust-nettle-7+default-dev, librust-regex-1+default-dev, 
> librust-thiserror-1+default-dev, 
> librust-unicode-normalization-0.1+default-dev (>= 0.1.9-~~), build-essential, 
> fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [622 B]
> Get:5 copy:/<>/apt_archive ./ Packages [685 B]
> Fetched 2270 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librust-dyn-clone-1+default-dev 
> but it is not installable
>Depends: librust-lalrpop-0.17+default-dev
>Depends: librust-nettle-7+default-dev
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://qa-logs.debian.net/2020/09/26/rust-sequoia-openpgp_0.18.0-1_unstable.log

A list of current common problems and possible solutions is available at

Bug#971103: marked as done (rust-sequoia-sqv: FTBFS: build-dependency not installable: librust-sequoia-openpgp-0.18+crypto-nettle-dev)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 23:10:00 -0400
with message-id <87lfg8w5fb@fifthhorseman.net>
and subject line Re: Bug#971103: rust-sequoia-sqv: FTBFS: build-dependency not 
installable: librust-sequoia-openpgp-0.18+crypto-nettle-dev
has caused the Debian Bug report #971103,
regarding rust-sequoia-sqv: FTBFS: build-dependency not installable: 
librust-sequoia-openpgp-0.18+crypto-nettle-dev
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.)


-- 
971103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-sequoia-sqv
Version: 0.18.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, 
> libstd-rust-dev, librust-anyhow-1+default-dev, 
> librust-chrono-0.4+default-dev, librust-clap-2+default-dev (>= 2.32.0-~~), 
> librust-sequoia-openpgp-0.18+crypto-nettle-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, 
> libstd-rust-dev, librust-anyhow-1+default-dev, 
> librust-chrono-0.4+default-dev, librust-clap-2+default-dev (>= 2.32.0-~~), 
> librust-sequoia-openpgp-0.18+crypto-nettle-dev, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [462 B]
> Get:5 copy:/<>/apt_archive ./ Packages [545 B]
> Fetched 1964 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: 
> librust-sequoia-openpgp-0.18+crypto-nettle-dev but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/09/26/rust-sequoia-sqv_0.18.0-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
On Sun 2020-09-27 20:38:50 +0200, Lucas Nussbaum wrote:
> Source: rust-sequoia-sqv
> Version: 0.18.0-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200926 ftbfs-bullseye

rust-sequoia-openpgp 0.18.0-1 is now in unstable, and rust-sequoia-sqv 0.18.0-2
is now building just fine on the buildd network.

 --dkg


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

Bug#971103: rust-sequoia-sqv: FTBFS: build-dependency not installable: librust-sequoia-openpgp-0.18+crypto-nettle-dev

[Daniel Kahn Gillmor]

On Sun 2020-09-27 20:38:50 +0200, Lucas Nussbaum wrote:
> Source: rust-sequoia-sqv
> Version: 0.18.0-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200926 ftbfs-bullseye

rust-sequoia-openpgp 0.18.0-1 is now in unstable, and rust-sequoia-sqv 0.18.0-2
is now building just fine on the buildd network.

 --dkg


signature.asc
Description: PGP signature

Bug#972208: marked as done (python-magcode-core FTBFS: error: failed to run pyversions)

[Debian Bug Tracking System]

Your message dated Thu, 15 Oct 2020 01:04:03 +
with message-id 
and subject line Bug#972208: fixed in python-magcode-core 1.5.4-4
has caused the Debian Bug report #972208,
regarding python-magcode-core FTBFS: error: failed to run pyversions
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.)


-- 
972208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-magcode-core
Version: 1.5.4-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=python-magcode-core=all=1.5.4-3=1600816365=0

...
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
dh_auto_clean
dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
dh_auto_clean: warning: Please use the third-party "pybuild" build system 
instead of python-distutils
dh_auto_clean: warning: This feature will be removed in compat 12.
Can't exec "pyversions": No such file or directory at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 124.
dh_auto_clean: error: failed to run pyversions
make[1]: *** [debian/rules:25: override_dh_auto_clean] Error 25
--- End Message ---
--- Begin Message ---
Source: python-magcode-core
Source-Version: 1.5.4-4
Done: Matthew Grant 

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

Debian distribution maintenance software
pp.
Matthew Grant  (supplier of updated python-magcode-core 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Oct 2020 11:20:52 +1300
Source: python-magcode-core
Architecture: source
Version: 1.5.4-4
Distribution: unstable
Urgency: medium
Maintainer: Matthew Grant 
Changed-By: Matthew Grant 
Closes: 972208
Changes:
 python-magcode-core (1.5.4-4) unstable; urgency=medium
 .
   * Convert to debian/rules to pybuild. (Closes: #972208)
Checksums-Sha1:
 e9b7a669eb508aa4d64d525d6cc6e8f521a02b54 2020 python-magcode-core_1.5.4-4.dsc
 89270eb024ea70dc034b5c521a69deb1f5e890c8 50211 
python-magcode-core_1.5.4.orig.tar.gz
 87153aa7fce2963af6a61040364ea31dfd795cab 4756 
python-magcode-core_1.5.4-4.debian.tar.xz
 005e0fc248dc5f1c20383deb5c60fa0377410614 7028 
python-magcode-core_1.5.4-4_amd64.buildinfo
Checksums-Sha256:
 cf7fada17da1574e93fd2f5bb6d01527743883527b1a3205a66b1722b6c686be 2020 
python-magcode-core_1.5.4-4.dsc
 00468a8e1a77a32bcc15e4291fcc1636544ff3d7975f033003968c991794d9ba 50211 
python-magcode-core_1.5.4.orig.tar.gz
 3c569133c9fd0633bb11d185b5efcf8f2c42511b00769ab67f683cb2fdc1607c 4756 
python-magcode-core_1.5.4-4.debian.tar.xz
 a93bfd7977aa97895d5ffef985f86758d7164f32d6f5eeab7bc55bb36e0579c9 7028 
python-magcode-core_1.5.4-4_amd64.buildinfo
Files:
 54788e8b8843a0713c73ea33e8c0edad 2020 python optional 
python-magcode-core_1.5.4-4.dsc
 0adacaefe9f359b71982eab5e5446d2f 50211 python optional 
python-magcode-core_1.5.4.orig.tar.gz
 e18d8c04e98d3ba4433c27b574052265 4756 python optional 
python-magcode-core_1.5.4-4.debian.tar.xz
 0fe4a86d32f37c702feb4f085c436edd 7028 python optional 
python-magcode-core_1.5.4-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEwaHD8RNdvgk2cFzjxE5f/BM1w6IFAl+HmrEWHG1hdHRAbWF0
dGdyYW50Lm5ldC5uegAKCRDETl/8EzXDonopD/9UFXEFa9Cni0KewmOJwCkw3V52
pKgJCUISUXDkpbhXszHaK0NcSpWltcvAc/cXjYE4mM8dPhx2Z5a7rsMy92GDxKuB
RgjWSN9Bc2oLaOPLfNFX3VbOjs43rbCzz+vqv1nOY4UMQEAIJJa+7amDsk7uuAcP
7EAjrNz7d9euQ4rg7MYfsZQ5NTUrKvbKx+tklTJfiYPVdtstU/RNs1iwDhrNACFN
d5pse82FSM0SxUb2oQVQswMgyft6m6+Hafi15uMxMRr1CLRGzexkMZ6rAAneJRj5
ZnVITsm2c3bV8gQMeAQWuK13u0T2qZxYByJTS5ztHHV4W670Bwvg75M9yDaCc01B
LR0bVeHQOBJY5PsfJGQPEWJi/m1YpH3fBN2un5G4J+O1IHAp2G1FERHrJR+DtWjX
jdbhcgr2X0eEbDWc7/SU6xaCfckqGXDLHZyyDttyTv1bzHSB7CR5YBqxwIYzlkot
aHwZ9uFqf6EBhPzSpiKr8xk8rtOu394BG1Dt+uWUvhGJ/kkzxPixFwTvx+O/q4Nk
cta5DfisBWw3QEpdiSAx9K7W6yi3YccaBgdmIKlkE/b/aSdQsc+zg6MhbhJGWzKi
ZxOzImZuDLLVqfgBn9F2m35a4wRq+OCx7QqREi7DSYW5e7Wnc2uoJd2Sf/zuDzyJ
n5v2NgivMrCTob9PHA==
=zhm7
-END PGP SIGNATURE End Message ---

Processed: closing 971119, closing 971124

[Debian Bug Tracking System]

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

> close 971119
Bug #971119 [src:rust-nettle-sys] rust-nettle-sys: FTBFS: unsatisfiable 
build-dependencies: librust-cexpr-0.3+default-dev (>= 0.3.3-~~), 
librust-clang-sys-0.28+clang-6-0-dev, librust-clang-sys-0.28+default-dev, 
librust-clang-sys-0.28+runtime-dev
Marked Bug as done
> close 971124
Bug #971124 [src:rust-nettle] rust-nettle: FTBFS: unsatisfiable 
build-dependencies: librust-cexpr-0.3+default-dev (>= 0.3.3-~~), 
librust-clang-sys-0.28+clang-6-0-dev, librust-clang-sys-0.28+default-dev, 
librust-clang-sys-0.28+runtime-dev
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#971119: closing 971119, closing 971124

[Daniel Kahn Gillmor]

close 971119 
close 971124 
thanks

These two FTBFS bug reports (for rust-nettle and rust-nettle-sys) were
happening because of #971139 on rust-bindgen.

When #971139 was resolved by rust-bindgen 0.51.1-5 (Sylvestre patched
the depenedencies in Cargo.toml), these other FTBFS bugs got solved as
well.

Bug#972185: libre0: stack smashing detected in v1.1.0

[Kevin Otte]

Thanks for the additional eyes. Should I file a bug against baresip to
have it rebuilt for testing, or will that be triggered automatically
when libre migrates?

On 10/14/20 12:40 PM, Bernhard Übelacker wrote:
> Dear Maintainer,
> I could reproduce the issue and it looks like there is a ABI break
> of libre0 because the size of struct sip_addr has changed
> from 152 bytes to 168, and therefore overwrites the stack canary here [1].
> 
> A baresip built agains libre0 1.1.0-1 did not show this problem.
> 
> Kind regards,
> Bernhard

Bug#972232: cctools FTBFS on i386 with glibc 2.31

[Adrian Bunk]

Source: cctools
Version: 7.1.2-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/history/i386/cctools.html
https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/i386/cctools.html
https://buildd.debian.org/status/logs.php?pkg=cctools=i386

...
parrot_helper.c:51:5: error: conflicting types for ‘gettimeofday’
   51 | int gettimeofday( struct timeval *tv, struct timezone *tz )
  | ^~~~
In file included from parrot_helper.c:20:
/usr/include/i386-linux-gnu/sys/time.h:66:12: note: previous declaration of 
‘gettimeofday’ was here
   66 | extern int gettimeofday (struct timeval *__restrict __tv,
  |^~~~
make[3]: *** [../../rules.mk:29: libparrot_helper.so] Error 1

Bug#972195: marked as done (python-setproctitle's tests fail in unstable)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 21:21:09 +
with message-id 
and subject line Bug#972195: fixed in python-setproctitle 1.1.10-3
has caused the Debian Bug report #972195,
regarding python-setproctitle's tests fail in unstable
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.)


-- 
972195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-setproctitle
Version: 1.1.10-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9


python-setproctitle's tests fail in unstable.

[...]
==
FAIL: No problem with encoded argv[0] path.
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.8_setproctitle/build/tests/setproctitle_test.py",
line 272, in test_weird_path
rv = self.run_script(r"""
  File
"/<>/.pybuild/cpython3_3.8_setproctitle/build/tests/setproctitle_test.py",
line 416, in run_script
self.fail("test script failed")
AssertionError: test script failed
 >> begin captured stdout << -
b''
b'/bin/sh: 1: /tmp/tmp5aaqs7oa/u20ac/u2603/python: not found\n'

- >> end captured stdout << --

[...]
==
FAIL: Title can contain unicode characters.
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.8_setproctitle/build/tests/setproctitle_test.py",
line 230, in test_unicode
self.fail("unexpected ps output: %r" % title)
AssertionError: unexpected ps output: 'Hello, ☃!'
--- End Message ---
--- Begin Message ---
Source: python-setproctitle
Source-Version: 1.1.10-3
Done: Gordon Ball 

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

Debian distribution maintenance software
pp.
Gordon Ball  (supplier of updated python-setproctitle 
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, 14 Oct 2020 20:31:27 +
Source: python-setproctitle
Architecture: source
Version: 1.1.10-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Gordon Ball 
Closes: 972195
Changes:
 python-setproctitle (1.1.10-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Gordon Ball ]
   * Fix FTBFS with multiple supported python versions (Closes: #972195)
Checksums-Sha1:
 0284e9fcfe6bf01fcd2fd2f4c15fc889ac987edb 2280 python-setproctitle_1.1.10-3.dsc
 b89ec74a4356111c2254a665fd028efb029f6948 4004 
python-setproctitle_1.1.10-3.debian.tar.xz
 71ccdcf423ef97a863fe71460ecd47ebab295f62 6459 
python-setproctitle_1.1.10-3_source.buildinfo
Checksums-Sha256:
 e39fb1d52f3307bc3593a653b07b27b84740c612d62454b2278e0320cc72521c 2280 
python-setproctitle_1.1.10-3.dsc
 a153e9d81511040df038fcdfefbe0a1f5e2aecf704e80c09d053320477fecf15 4004 
python-setproctitle_1.1.10-3.debian.tar.xz
 40da5d12a7f764b8f33c3d81819e29037e4b9efd037affeeae4fa7c03ada46d7 6459 
python-setproctitle_1.1.10-3_source.buildinfo
Files:
 2b65f4c6662a0ebc46757b80f6b16752 2280 python optional 
python-setproctitle_1.1.10-3.dsc
 5cf9d373e329732a52e6a07668d142af 4004 python optional 
python-setproctitle_1.1.10-3.debian.tar.xz
 31360bfbfb7434a032bfdc885e69407a 6459 python optional 
python-setproctitle_1.1.10-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6PwpXIa418BJ+Xuno12v+60p6N4FAl+HYckACgkQo12v+60p
6N4ByQ/7Bmi0z3/YMDABHkFJTEI6ju0Wcy70qh59PI5mlgkgXyOUwX5dZwmLYRyP
0LGaW3pV6agkBtDYaQHRXVwtYyKUoDebBgDUyXldswlzGAGbX8f+1p4rlxJ/DmEK
51nmPN6mGzth+iTpkOrU4n3eNXTk96mu/UpQssVSwnnW9x0UWJ65h3BY4oLMryam
oV1TR0yGM23A+jBSlp19FGjkA2HYWTPjVty6YtA6By3TFr54Qjp4j167cxmQ/2H4

Bug#972230: CVE-2017-17742 CVE-2019-16201 CVE-2019-16254 CVE-2019-16255 CVE-2020-25613

[Moritz Muehlenhoff]

Package: jruby
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

jruby bundles various modules from the Ruby stdlib, which have been affected by
security issues:

CVE-2017-17742:
https://www.ruby-lang.org/en/news/2018/03/28/http-response-splitting-in-webrick-cve-2017-17742/
https://github.com/ruby/ruby/commit/d9d4a28f1cdd05a0e8dabb36d747d40bbcc30f16

CVE-2019-16201
https://github.com/ruby/ruby/commit/36e057e26ef2104bc2349799d6c52d22bb1c7d03
https://hackerone.com/reports/661722
https://www.ruby-lang.org/en/news/2019/10/01/webrick-regexp-digestauth-dos-cve-2019-16201/

CVE-2019-16254
https://github.com/ruby/ruby/commit/3ce238b5f9795581eb84114dcfbdf4aa086bfecc
https://hackerone.com/reports/331984
https://www.ruby-lang.org/en/news/2019/10/01/http-response-splitting-in-webrick-cve-2019-16254/

CVE-2019-16255
https://www.ruby-lang.org/en/news/2019/10/01/code-injection-shell-test-cve-2019-16255/
https://github.com/ruby/ruby/commit/3af01ae1101e0b8815ae5a106be64b0e82a58640

CVE-2020-25613
https://www.ruby-lang.org/en/news/2020/09/29/http-request-smuggling-cve-2020-25613/
https://github.com/ruby/webrick/commit/8946bb38b4d87549f0d99ed73c62c41933f97cc7


The root cause for all of this is #926280

Cheers,
Moritz

Bug#972228: CVE-2020-13991

[Moritz Muehlenhoff]

Package: iotjs
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13991 is for
JerryScript, which iotjs appears to included.

Cheers,
Moritz

Bug#972185: libre0: stack smashing detected in v1.1.0

[Bernhard Übelacker]

Dear Maintainer,
I could reproduce the issue and it looks like there is a ABI break
of libre0 because the size of struct sip_addr has changed
from 152 bytes to 168, and therefore overwrites the stack canary here [1].

A baresip built agains libre0 1.1.0-1 did not show this problem.

Kind regards,
Bernhard


[1]
(rr) bt
#0  0x7f9dc0bf22eb in memset (__len=168, __ch=0, __dest=0x7fff4bc3ae80) at 
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:71
#1  sip_addr_decode (addr=addr@entry=0x7fff4bc3ae80, 
pl=pl@entry=0x7fff4bc3af50) at src/sip/addr.c:32
#2  0x556a958a831c in call_connect (call=0x556a95dbb7a0, 
paddr=paddr@entry=0x7fff4bc3af50) at src/call.c:932
#3  0x556a958b635c in ua_connect (ua=0x556a95db6940, callp=callp@entry=0x0, 
from_uri=from_uri@entry=0x0, req_uri=req_uri@entry=0x556a95dbd5a0 "sip:", '0' 
, "@fritz.box", vmode=vmode@entry=VIDMODE_ON) at src/ua.c:928
#4  0x7f9dc02a5e1f in dial_handler (pf=, arg=0x7fff4bc3b030) 
at modules/menu/menu.c:266
#5  0x556a9586 in cmd_report (data=0x0, mb=, 
pf=0x7f9dc0c66020 , cmd=0x7f9dc02aa8c0 ) at src/cmd.c:293
#6  cmd_process_edit (commands=, ctxp=, 
key=, pf=, data=0x0) at src/cmd.c:389
#7  0x556a958aaf74 in cmd_process (commands=, 
ctxp=, key=, pf=pf@entry=0x7f9dc0c66020 
, data=data@entry=0x0) at src/cmd.c:539
#8  0x556a958b7fe0 in ui_input_key (uis=, key=key@entry=10 
'\n', pf=pf@entry=0x7f9dc0c66020 ) at src/ui.c:66
#9  0x7f9dc0c6348a in report_key (ui=, key=10 '\n') at 
modules/stdio/stdio.c:66
#10 ui_fd_handler (flags=, arg=) at 
modules/stdio/stdio.c:90
#11 0x7f9dc0c312dc in fd_poll (re=re@entry=0x7f9dc0c5d0e0 ) at 
src/main/main.c:896
#12 0x7f9dc0c31d52 in re_main (signalh=0x556a958babd0 ) at 
src/main/main.c:1030
#13 0x556a958a052f in main (argc=, argv=) at 
src/main.c:301


# Unstable amd64 qemu VM 2020-10-14


apt update
apt dist-upgrade


apt install systemd-coredump mc htop fakeroot gdb rr baresip 
baresip-core-dbgsym libre0-dbgsym
apt build-dep libre0
apt build-dep baresip
echo 1 > /proc/sys/kernel/perf_event_paranoid




mkdir /home/benutzer/source/libre0/orig -p
cd/home/benutzer/source/libre0/orig
apt source libre0
cd

mkdir /home/benutzer/source/baresip-core/orig -p
cd/home/benutzer/source/baresip-core/orig
apt source baresip-core
cd




baresip
d
sip:...@fritz.box



benutzer@debian:~$ baresip
baresip v1.0.0 Copyright (C) 2010 - 2020 Alfred E. Heggestad et al.
Local network address:  IPv4=ens4|10.0.2.15  IPv6=ens4|fec0::5054:ff:fe12:3456
aucodec: PCMU/8000/1
aucodec: PCMA/8000/1
ausrc: alsa
auplay: alsa
medianat: stun
medianat: turn
medianat: ice
Populated 1 account
Populated 3 contacts
Populated 2 audio codecs
Populated 0 audio filters
Populated 0 video codecs
Populated 0 video filters
baresip is ready.
>sip:...@fritz.box
ua: using best effort AF: af=AF_INET
call: connecting to 'sip:...@fritz.box'..
*** stack smashing detected ***: terminated
Abgebrochen (Speicherabzug geschrieben)



root@debian:~# journalctl -e
...
Okt 14 17:49:57 debian systemd[1]: Started Process Core Dump (PID 11453/UID 0).
Okt 14 17:49:58 debian systemd-coredump[11454]: Process 11451 (baresip) of user 
1000 dumped core.

Stack trace of thread 11451:
#0  0x7f7c802e8c41 
__GI_raise (libc.so.6 + 0x3bc41)
#1  0x7f7c802d2537 
__GI_abort (libc.so.6 + 0x25537)
#2  0x7f7c8032b6c8 
__libc_message (libc.so.6 + 0x7e6c8)
#3  0x7f7c803ba5b2 
__GI___fortify_fail (libc.so.6 + 0x10d5b2)
#4  0x7f7c803ba590 
__stack_chk_fail (libc.so.6 + 0x10d590)
#5  0x55ccf95ed3da 
call_connect (baresip + 0x143da)
#6  0x55ccf95fb35c 
ua_connect (baresip + 0x2235c)
#7  0x7f7c7fdb9e1f n/a 
(menu.so + 0x4e1f)
#8  0x55ccf95efaa6 n/a 
(baresip + 0x16aa6)
#9  0x7f7c8067348a n/a 
(stdio.so + 0x148a)
#10 0x7f7c8063f2dc n/a 
(libre.so.0 + 0x562dc)
#11 0x7f7c8063fd52 re_main 
(libre.so.0 + 0x56d52)
#12 0x55ccf95e552f main 
(baresip + 0xc52f)
#13 0x7f7c802d3cca 
__libc_start_main (libc.so.6 + 0x26cca)
#14 0x55ccf95e56ba _start 
(baresip + 0xc6ba)
Okt 14 17:49:58 debian systemd[1]: systemd-coredump@2-11453-0.service: 
Succeeded.



root@debian:~# coredumpctl 

Processed: Re: Bug#971687: Bug#971668: libsane: broke ABI

[Debian Bug Tracking System]

Processing control commands:

> reopen 908681
Bug #908681 {Done: Jörg Frings-Fürst } [libsane1] libsane1: 
pointless package rename
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.0.27-3.1.

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

Bug#972206: remctl ftbfs in unstable (failing tests)

[Russ Allbery]

Matthias Klose  writes:

> https://buildd.debian.org/status/fetch.php?pkg=remctl=amd64=3.16-4%2Bb7=1602646591=0

> [...]
> make  check-local
> make[2]: Entering directory '/<>'
> tests/runtests -l '/<>/tests/TESTS'

Thanks, this is probably because that's one of the buildds with only IPv6
addresses.  Working on a fix, will try to get it uploaded soon since I
know a Python transition is coming.

-- 
Russ Allbery (r...@debian.org)  

Processed: closing 963661

[Debian Bug Tracking System]

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

> close 963661 0.16.0.159.g483ce16-1~exp1
Bug #963661 [src:ufo-filters] ufo-filters: FTBFS with Sphinx 3.1: ImportError: 
cannot import name 'l_' from 'sphinx.locale' 
(/usr/lib/python3/dist-packages/sphinx/locale/__init__.py)
Marked as fixed in versions ufo-filters/0.16.0.159.g483ce16-1~exp1.
Bug #963661 [src:ufo-filters] ufo-filters: FTBFS with Sphinx 3.1: ImportError: 
cannot import name 'l_' from 'sphinx.locale' 
(/usr/lib/python3/dist-packages/sphinx/locale/__init__.py)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#971773: marked as done (Needs porting to PostgreSQL 13)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 19:03:59 +
with message-id 
and subject line Bug#971773: fixed in gvmd 9.0.1-4.1
has caused the Debian Bug report #971773,
regarding Needs porting to PostgreSQL 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.)


-- 
971773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gvmd
Version: 9.0.1-4
Severity: important

Hi,

PostgreSQL is moving to version 13, and gvmd's autopkgtest in testing
seems to have a problem with that:

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gvmd/733/log.gz

autopkgtest [23:52:15]: test test: [---
-- Configuring Greenbone Vulnerability Manager...
-- The C compiler identification is GNU 10.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2")
-- Could NOT find Git (missing: GIT_EXECUTABLE)
-- Install prefix: /usr/local
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Checking for module 'libgvm_base>=11.0.1'
--   Found libgvm_base, version 11.0.1
-- Checking for module 'libgvm_util>=11.0.1'
--   Found libgvm_util, version 11.0.1
-- Checking for module 'libgvm_osp>=11.0.1'
--   Found libgvm_osp, version 11.0.1
-- Checking for module 'libgvm_gmp>=11.0.1'
--   Found libgvm_gmp, version 11.0.1
-- Checking for module 'gnutls>=3.2.15'
--   Found gnutls, version 3.6.15
-- Checking for module 'glib-2.0>=2.42'
--   Found glib-2.0, version 2.66.0
-- Checking for module 'libical>=1.00'
--   Found libical, version 3.0.8
-- Looking for PostgreSQL...
CMake Error at 
/usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:165 (message):
  Could NOT find PostgreSQL (missing: PostgreSQL_TYPE_INCLUDE_DIR) (found
  version "13.0")
Call Stack (most recent call first):
  /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:458 
(_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.18/Modules/FindPostgreSQL.cmake:247 
(find_package_handle_standard_args)
  src/CMakeLists.txt:44 (find_package)


-- Configuring incomplete, errors occurred!
See also 
"/tmp/autopkgtest-lxc.u04wvbq7/downtmp/build.32A/src/build/CMakeFiles/CMakeOutput.log".
See also 
"/tmp/autopkgtest-lxc.u04wvbq7/downtmp/build.32A/src/build/CMakeFiles/CMakeError.log".
autopkgtest [23:52:16]: test test: ---]
autopkgtest [23:52:16]: test test:  - - - - - - - - - - results - - - - - - - - 
- -
test FAIL non-zero exit status 1

Please tend to this problem soon, it is one of the blockers on getting
PostgreSQL 13 into testing.

Christoph
--- End Message ---
--- Begin Message ---
Source: gvmd
Source-Version: 9.0.1-4.1
Done: Christoph Berg 

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated gvmd 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, 14 Oct 2020 20:45:36 +0200
Source: gvmd
Architecture: source
Version: 9.0.1-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Christoph Berg 
Closes: 971773
Changes:
 gvmd (9.0.1-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/tests: Set -DPostgreSQL_TYPE_INCLUDE_DIR=/usr/include/postgresql as
 debian/rules already does. Fixes test failure with PostgreSQL 13.
 (Closes: #971773)
Checksums-Sha1:
 47df894768f5438494a8cdbd46354c3d8e410128 2212 gvmd_9.0.1-4.1.dsc
 561964fcac29b7fae4f366b4d1affe6b4764722a 20196 gvmd_9.0.1-4.1.debian.tar.xz
Checksums-Sha256:
 

Bug#971669: libopenmpi3: armel mipsel: mca_pmix_pmix3x.so: undefined symbol: OPAL_MCA_PMIX3X_PMIx_Get_version

[Drew Parsons]

Source: openmpi
Followup-For: Bug #971669

As far as pmix_ext3x.so goes, the other arches are picking it up from
--with-pmix=/usr/lib//pmix2  (i.e.--with-pmix=$(LIBDIR)/pmix2)
added to dh_auto_configure in the PMIX variable in debian/rules.

This external pmix is excluded from armel and mipsel by
  NO_PMIX_ARCH:= armel mipsel

On your abel build, did you change the setting of NO_PMIX_ARCH?

/usr/lib/arm-linux-gnueabi/pmix2/ is available for armel (and
mipsel).  Was breaking it breaking openmpi on those arches?

Not sure if that explains why _Get_version is undefined in
mca_pmix_pmix3x.so, but it might explain why _ext3x.so isn't being
built on the buildd.

Bug#971773: Needs porting to PostgreSQL 13

[Christoph Berg]

NMU diff: https://salsa.debian.org/pkg-security-team/gvmd/-/merge_requests/1

Christoph

Bug#972220: src:cgreen: fails to migrate to testing for too long: FTBFS on s390x

[Paul Gevers]

Source: cgreen
Version: 1.2.0-2
Severity: serious
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:cgreen in its
current version in unstable has been trying to migrate for 61 days [2].
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=cgreen




signature.asc
Description: OpenPGP digital signature

Bug#969648: Bug#972033: python3.9, dask, pandas 1.1

[Matthias Klose]

On 10/14/20 9:47 AM, Rebecca N. Palmer wrote:
> Control: severity 969648 serious
> Control: tags 969650 pending
> Control: tags 972033 pending
> 
> Python 3.9 related breakage has been declared RC, so if nobody objects,  I
> intend to upload pandas 1.1 to unstable (possibly tonight, but it probably 
> won't
> build before numpy and matplotlib are binNMUd for Python 3.9) despite the dask
> breakage.
> 
> As noted in #969648, it is likely that dask can be fixed, but this has not 
> been
> tested in Debian.  (Testing dask also currently fails for lack of a Python 3.9
> numpy.)

please wait until the required binNMUs are done.

Bug#971910: marked as done (fix ftbfs with python3.9)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 17:51:37 +
with message-id 
and subject line Bug#971910: fixed in python-cffi 1.14.3-2
has caused the Debian Bug report #971910,
regarding fix ftbfs with python3.9
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.)


-- 
971910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-cffi
Version: 1.14.3-1
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.9

fix ftbfs with python3.9, patch at
https://launchpadlibrarian.net/501211180/python-cffi_1.14.2-1_1.14.3-1ubuntu0.1.diff.gz
--- End Message ---
--- Begin Message ---
Source: python-cffi
Source-Version: 1.14.3-2
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated python-cffi 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, 14 Oct 2020 09:34:33 -0700
Source: python-cffi
Architecture: source
Version: 1.14.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Stefano Rivera 
Closes: 971910
Changes:
 python-cffi (1.14.3-2) unstable; urgency=medium
 .
   * Revert the temporary NMU hack: Ignore test results for a first build.
   * Patch: Fix a crash in tests under python3.9-dbg. (Closes: #971910)
   * Update upstream metadata to point to heptapod.
Checksums-Sha1:
 c1bd0f3f1138154ed3a90a3cfce65e064a69c358 1871 python-cffi_1.14.3-2.dsc
 3f6f65e469048bf5b01ebd5f57d508784cbce513 7496 
python-cffi_1.14.3-2.debian.tar.xz
 3d5dd6927a3902aaeed30bbeaf6d56f035a9f4a5 7437 
python-cffi_1.14.3-2_source.buildinfo
Checksums-Sha256:
 692adbc49bd32aeec5b5d40d025b7d76d5bb29a09dc3747b33436a00f4936aeb 1871 
python-cffi_1.14.3-2.dsc
 48c3a851577d942188be6892ba92b037b0d3e2a52abc40ac9f1b3a87a03e 7496 
python-cffi_1.14.3-2.debian.tar.xz
 92039a0501f6dbe727c48218f173171527f874d19729ef1de663f8fa8bb76359 7437 
python-cffi_1.14.3-2_source.buildinfo
Files:
 edadd46518451b6f4bf0a3335a73f9b2 1871 python optional python-cffi_1.14.3-2.dsc
 55d4df778a41f4fdeb9ad07759c13389 7496 python optional 
python-cffi_1.14.3-2.debian.tar.xz
 1ce24d1a87bc9d9b8059ed2a2c1d7ccd 7437 python optional 
python-cffi_1.14.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQTumtb5BSD6EfafSCRHew2wJjpU2AUCX4c0FQAKCRBHew2wJjpU
2OT1AP0VwRpmGvKfs8zDEYL73PR8as3YN7HTpZ1AqfMr8/W0/gEAulsFB9/5pHcw
czV5zGRy19Tq9CYDD9ojAbb+BA71BAY=
=CWWD
-END PGP SIGNATURE End Message ---

Processed: Bug#971910 marked as pending in python-cffi

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #971910 [src:python-cffi] fix ftbfs with python3.9
Added tag(s) pending.

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

Bug#971910: marked as pending in python-cffi

[Stefano Rivera]

Control: tag -1 pending

Hello,

Bug #971910 in python-cffi reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-cffi/-/commit/15a361ea79e215b35977936d9c56f4e1b4f4dde3


Patch: Fix a crash in tests under python3.9-dbg. (Closes: #971910)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/971910

Bug#972217: python-crc32c FTBFS on arm64

[Adrian Bunk]

Source: python-crc32c
Version: 2.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=python-crc32c=arm64=2.1-1=1601652233=0

...
   dh_auto_build -a -O--buildsystem=pybuild -O--test-pytest
I: pybuild base:217: /usr/bin/python3 setup.py build
running build
running build_ext
platform: aarch64, is_intel: 0, is_arm: 1
building 'crc32c' extension
creating build
creating build/temp.linux-arm64-3.8
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -DNDEBUG -DIS_ARM -I. -I/usr/include/python3.8 -c 
_crc32c.c -o build/temp.linux-arm64-3.8/_crc32c.o -O3 -march=armv8-a+crc+crypto
_crc32c.c: In function ‘PyInit_crc32c’:
_crc32c.c:150:11: warning: implicit declaration of function 
‘_crc32c_arm64_probe’; did you mean ‘_crc32c_intel_probe’? 
[-Wimplicit-function-declaration]
  150 |  else if (_crc32c_arm64_probe()) {
  |   ^~~
  |   _crc32c_intel_probe
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -DNDEBUG -DIS_ARM -I. -I/usr/include/python3.8 -c 
checkarm.c -o build/temp.linux-arm64-3.8/checkarm.o -O3 
-march=armv8-a+crc+crypto
In file included from /usr/include/aarch64-linux-gnu/sys/auxv.h:25,
 from checkarm.c:27:
checkarm.c: In function ‘_crc32c_arm64_probe’:
checkarm.c:32:22: error: expected identifier or ‘(’ before numeric constant
   32 |  const unsigned long HWCAP_CRC32 = 1 << 7;
  |  ^~~
error: command 'aarch64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:352: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p 3.8 returned exit 
code 13

Processed: found 972206 in 3.16-4

[Debian Bug Tracking System]

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

> found 972206 3.16-4
Bug #972206 [src:remctl] remctl FTBFS on IPV6-only buildds
Marked as found in versions remctl/3.16-4.
> thanks
Stopping processing here.

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

Processed: notfound 972206 in 4.16-3

[Debian Bug Tracking System]

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

> notfound 972206 4.16-3
Bug #972206 [src:remctl] remctl FTBFS on IPV6-only buildds
The source 'remctl' and version '4.16-3' do not appear to match any binary 
packages
No longer marked as found in versions remctl/4.16-3.
> thanks
Stopping processing here.

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

Bug#972216: nmap: New NPSL 0.92 license likely non-free

[Göran Weinholt]

Package: nmap
Version: 7.91+dfsg1-1
Severity: serious
Justification: DFSG

(Please downgrade or close if I'm wrong about this. I saw on
guix-devel that nmap has a new license and they believe it's non-free,
which I agree with, but I'm no expert, and I'm just filing this bug to
have more eyes on the issue).

Dear maintainer,

The latest nmap is under a new license that seems to go against
DFSG § 1 (Free Redistribution) seems to be intended to go against
DFSG § 6 (No Discrimination Against Fields of Endeavor), and it
could also be argued that it goes against DFSG § 9 (License Must
Not Contaminate Other Software).

An annotated version of the license is available online here:


This line from the annotation is pretty clear:

| Proprietary vendors: This license does not allow you to redistribute
| Nmap source code or the executable for use with your software (stand
| alone or on an appliance). We do sell licenses which permit this,
| and also include support and updates. Dozens of software vendors
| already license Nmap technology such as host discovery, port
| scanning, OS detection, version detection, and the Nmap Scripting
| Engine. Contact sa...@nmap.com for a quote.

I did a cursory reading and the trouble mainly seems to come from the
section on derivative works, which has been extended beyond what is
commonly accepted in the community. "Licensor interprets that term
quite broadly," they write, and annotate it with this:

| The idea here is to prevent companies from using open source Nmap in
| their proprietary software or appliances. Some have in the past
| distributed Nmap executables as part of expensive proprietary
| products and refused to make the source available, claiming a
| loophole based on strange interpretations of the GPL definition of
| derivative and collective works. If companies take value from Nmap,
| they need to contribute back to the project and the open source
| community by either making their product/project compatible open
| source or buying a commercial license.

As an example, a proprietary program cannot, according to § 3 of NPSL
0.92, run nmap and parse the output. Even just reading nmap's data
files turns a program into a derivative work. I don't think our users
would accept us leaving such a copyright land mine in main.

Processed: retitle 972206 to remctl FTBFS on IPV6-only buildds

[Debian Bug Tracking System]

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

> retitle 972206 remctl FTBFS on IPV6-only buildds
Bug #972206 [src:remctl] remctl ftbfs in unstable (failing tests)
Changed Bug title to 'remctl FTBFS on IPV6-only buildds' from 'remctl ftbfs in 
unstable (failing tests)'.
> thanks
Stopping processing here.

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

Processed: tagging 972206

[Debian Bug Tracking System]

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

> tags 972206 + ftbfs
Bug #972206 [src:remctl] remctl ftbfs in unstable (failing tests)
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 971995

[Debian Bug Tracking System]

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

> tags 971995 + ftbfs
Bug #971995 [src:python-greenlet] python-greenlet ftbfs with python3-defaults 
(python3.9) from experimental
Bug #972025 [src:python-greenlet] python-greenlet ftbfs with python3.9 as 
supported python version
Added tag(s) ftbfs.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 972026

[Debian Bug Tracking System]

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

> tags 972026 + ftbfs
Bug #972026 [src:python-pyo] python-pyo ftbfs with python3.9 as supported 
python version
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 972029

[Debian Bug Tracking System]

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

> tags 972029 + ftbfs
Bug #972029 [src:python-udatetime] python-udatetime ftbfs with python3.9 as 
supported python3 version
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 972195

[Debian Bug Tracking System]

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

> tags 972195 + ftbfs
Bug #972195 [src:python-setproctitle] python-setproctitle's tests fail in 
unstable
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 957471

[Debian Bug Tracking System]

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

> tags 957471 + ftbfs
Bug #957471 [src:librcsb-core-wrapper] librcsb-core-wrapper: ftbfs with GCC-10
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#972025: python-greenlet ftbfs with python3.9 as supported python version

[Matthias Klose]

v 0.4.17 now uploaded to the delayed queue

Bug#970419: lilyterm: No longer starts (likely related to VTE changes)

[Philipp Wolski]

Had the same assertion in vte_terminal_spawn_sync, happens in Upstream too.

Dug around the envv Pointer, _vte_pty_check_envv does not like empty 
entries.


src/notebook.c is constructing the envv Pointer in environ_str and later 
copies it to new_environs.


Around line 150 there is a '\t' being pushed into environ_str but the 
following append of the TERM envvar is eventually ifdef'ed.
When COLORTERM is forced-pushed into environ_str another '\t' will be 
prefixed without checking environ_str again.


So unless you compile with ENABLE_SET_EMULATION there will be a lone 
'\t' in environ_str which will later be translated into an empty envv entry.


I supposed the check for non-empty environ_str should be within the 
ifdef as well before the COLORTERM append.

I attached a quick'n'dirty patch.

But now that I look at it again (7 hours later), it would also work to 
leave the code as is but hardcode a '\t' after the TERM append and 
remove the hardcoded '\t' from COLORTERM instead.

E.g.:
g_string_append_printf (environ_str, "TERM=xterm"); to 
g_string_append_printf (environ_str, "TERM=xterm\t"); etc

and
g_string_append_printf (environ_str, "\tCOLORTERM=lilyterm"); to 
g_string_append_printf (environ_str, "COLORTERM=lilyterm");


I'll leave that for upstream to figure out ;-)

Hope this helps someone.


Description: Prevent empty environ_str entry

Author: Philipp Wolski 
Bug-Debian: https://bugs.debian.org/970419
Last-Update: 2020-10-14

Index: lilyterm-0.9.9.4+git20150208.f600c0/src/notebook.c
===
--- lilyterm-0.9.9.4+git20150208.f600c0.orig/src/notebook.c
+++ lilyterm-0.9.9.4+git20150208.f600c0/src/notebook.c
@@ -148,14 +148,14 @@ struct Page *add_page(struct Window *win
 			environ_str = g_string_append(environ_str, "\t");
 		g_string_append_printf (environ_str, "%s", user_environ);
 	}
+
+#ifdef ENABLE_SET_EMULATION
 #ifdef SAFEMODE
 	if (environ_str && environ_str->len)
 #else
 	if (environ_str->len)
 #endif
 		environ_str = g_string_append(environ_str, "\t");
-
-#ifdef ENABLE_SET_EMULATION
 #  ifdef SAFEMODE
 	if (win_data->emulate_term == NULL)
 		g_string_append_printf (environ_str, "TERM=xterm");
@@ -163,8 +163,15 @@ struct Page *add_page(struct Window *win
 #  endif
 		g_string_append_printf (environ_str, "TERM=%s", win_data->emulate_term);
 #endif
+
+#ifdef SAFEMODE
+	if (environ_str && environ_str->len)
+#else
+	if (environ_str->len)
+#endif
+		environ_str = g_string_append(environ_str, "\t");
 	// set colorterm
-	g_string_append_printf (environ_str, "\tCOLORTERM=lilyterm");
+	g_string_append_printf (environ_str, "COLORTERM=lilyterm");
 
 //  Setting the VTE_CJK_WIDTH environment  //
 

Processed: tagging 972016

[Debian Bug Tracking System]

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

> tags 972016 + ftbfs
Bug #972016 [src:py-lmdb] py-lmdb ftbfs with python3.9
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 967169

[Debian Bug Tracking System]

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

> tags 967169 + ftbfs
Bug #967169 [src:libtorrent-rasterbar] libtorrent-rasterbar: Unversioned Python 
removal in sid/bullseye
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#971116: marked as done (ruby-rspec-puppet: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error:)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 15:34:24 +
with message-id 
and subject line Bug#971116: fixed in ruby-rspec-puppet 2.7.8-4
has caused the Debian Bug report #971116,
regarding ruby-rspec-puppet: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error:
to be marked as done.

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

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


-- 
971116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rspec-puppet
Version: 2.7.8-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> Failure/Error:
>   def get_env(name, mode = default_env)
> if RSpec::Puppet.rspec_puppet_example?
>   # use the actual platform, not the pretended
>  old_get_env(name, Platform.actual_platform)
> else
>  old_get_env(name, mode)
> end
> 
> NameError:
>   undefined local variable or method `default_env' for Puppet::Util:Module
> # ./lib/rspec-puppet/monkey_patches.rb:139:in `get_env'
> # ./lib/rspec-puppet.rb:77:in `block in '
> # ./lib/rspec-puppet.rb:34:in `'
> # ./lib/rspec-puppet/monkey_patches.rb:350:in `require'
> # ./spec/spec_helper.rb:11:in `'
> # ./lib/rspec-puppet/monkey_patches.rb:350:in `require'
> # ./spec/unit/monkey_patches_spec.rb:1:in `'
> 
> Finished in 0.4 seconds (files took 1.44 seconds to load)
> 0 examples, 0 failures, 87 errors occurred outside of examples
> 
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec 
> --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/09/26/ruby-rspec-puppet_2.7.8-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: ruby-rspec-puppet
Source-Version: 2.7.8-4
Done: Daniel Leidert 

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated ruby-rspec-puppet 
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, 14 Oct 2020 17:08:09 +0200
Source: ruby-rspec-puppet
Architecture: source
Version: 2.7.8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Daniel Leidert 
Closes: 971116
Changes:
 ruby-rspec-puppet (2.7.8-4) unstable; urgency=medium
 .
   * Team upload.
   * d/patches/002_Fix-Ruby2.7-FrozenError.patch: Add Applied-Upstream field.
   * d/patches/003-Fix-issues-with-puppet-gem-removal-of-default_env.patch: Add
 to fix FTBFS with puppet removal of `default_env` (closes: #971116).
   * d/patches/series: Enable new patch.
Checksums-Sha1:
 8ae26cd0b454a7858b0754b38dd48ebcd086741b 2092 ruby-rspec-puppet_2.7.8-4.dsc
 dc33f6db0b6c6cc359c7ac6b90fc5cfb078b49b8 4996 
ruby-rspec-puppet_2.7.8-4.debian.tar.xz
 22111bff7608f59f09239182656cccb361394dfe 9850 
ruby-rspec-puppet_2.7.8-4_amd64.buildinfo
Checksums-Sha256:
 f052f27dbe4c315bf9b4738755d2f621a69b1e39ec33a75b15708f2cde561947 2092 
ruby-rspec-puppet_2.7.8-4.dsc
 a67d3255ba06c83cd4bdcebaddfe102bca0e1ad20dad2fe72b2620bdfdcb04bd 4996 
ruby-rspec-puppet_2.7.8-4.debian.tar.xz
 83ccd6caf33e153f414ae78d2ac80cc38c80fc892e3af6fa2a09c781fe6363d1 9850 
ruby-rspec-puppet_2.7.8-4_amd64.buildinfo
Files:
 a109a3ecd1ba8a2ff3eac741b6427173 2092 ruby optional 
ruby-rspec-puppet_2.7.8-4.dsc
 9177ae082b154c694207b0a941924e10 4996 ruby optional 

Processed: tagging 971936

[Debian Bug Tracking System]

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

> tags 971936 + ftbfs
Bug #971936 [src:blist] blist ftbfs with python3-defaults (python3.9) from 
experimental
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: Bug#971116 marked as pending in ruby-rspec-puppet

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #971116 [src:ruby-rspec-puppet] ruby-rspec-puppet: FTBFS: ERROR: Test 
"ruby2.7" failed: Failure/Error:
Added tag(s) pending.

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

Bug#962194: lintian-brush: autopkgtest failure on s390x

[Gianfranco Costamagna]

Hello,


> https://yaml.readthedocs.io/en/latest/basicuse.html#more-examples
> 
> from ruamel.yaml import YAML
> 
> yaml=YAML(typ="safe", pure=True)
> yaml.load(f)
> 
> If that works, then we might be able to make a workaround to default to the
> pure Python version on big endian systems. To be reverted once upstream has
> a proper fix to the cpython code, of course.
> 
> Note: ruamel.yaml is mostly a one person (Anthon van der Neut) project, so
> a fix might take a while. Fans of s390x and other big endian architectures
> are very welcome to develop a patch!
> 
> https://yaml.readthedocs.io/en/latest/contributing.html
> 

not sure if I did it right, but this code:

#!/usr/bin/python3
from io import BytesIO
from ruamel.yaml import YAML
yaml = YAML(typ='safe', pure=True)

f = BytesIO(b"""\
format: multiarch-hints-1.0
hints:
- binary: coinor-libcoinmp-dev
  description: coinor-libcoinmp-dev conflicts on ...
  link: https://wiki.debian.org/MultiArch/Hints#file-conflict
  severity: high
  source: coinmp
  version: 1.8.3-2+b11
""")
yaml.load(f)


works now
thanks!

Gianfranco

Bug#971116: marked as pending in ruby-rspec-puppet

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #971116 in ruby-rspec-puppet reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/ruby-team/ruby-rspec-puppet/-/commit/093fadcc1b952dc38e421c836b8531258525750a


Add patch to fix FTBFS with puppet removal of `default_env`

  * d/patches/003-Fix-issues-with-puppet-gem-removal-of-default_env.patch: Add
to fix FTBFS with puppet removal of `default_env` (closes: #971116).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/971116

Bug#971130: marked as done (djangorestframework-gis: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 --system=custom "--test-args=cd {build_dir}; {interpreter} tests/manage.py tes

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 15:19:56 +
with message-id 
and subject line Bug#971130: fixed in djangorestframework-gis 0.16-1
has caused the Debian Bug report #971130,
regarding djangorestframework-gis: FTBFS: dh_auto_test: error: pybuild --test 
-i python{version} -p 3.8 --system=custom "--test-args=cd {build_dir}; 
{interpreter} tests/manage.py test tests/django_restframework_gis_tests" 
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.)


-- 
971130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: djangorestframework-gis
Version: 0.14-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 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_test -- --system=custom --test-args="cd {build_dir}; {interpreter} 
> tests/manage.py test tests/django_restframework_gis_tests"
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.8_djangorestframework-gis/build; 
> python3.8 tests/manage.py test tests/django_restframework_gis_tests
> Creating test database for alias 'default'...
> ..s.s.s..s.../usr/lib/python3/dist-packages/rest_framework/pagination.py:200:
>  UnorderedObjectListWarning: Pagination may yield inconsistent results with 
> an unordered object_list:  'django_restframework_gis_tests.models.Location'> QuerySet.
>   paginator = self.django_paginator_class(queryset, page_size)
> ..E...
> ==
> ERROR: test_post_location_list_EWKT 
> (django_restframework_gis_tests.tests.TestRestFrameworkGis)
> --
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 82, 
> in _execute
> return self.cursor.execute(sql)
>   File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", 
> line 381, in execute
> return Database.Cursor.execute(self, query)
> sqlite3.OperationalError: no such function: lwgeom_version
> 
> The above exception was the direct cause of the following exception:
> 
> Traceback (most recent call last):
>   File 
> "/<>/.pybuild/cpython3_3.8_djangorestframework-gis/build/tests/django_restframework_gis_tests/tests.py",
>  line 149, in test_post_location_list_EWKT
> response = self.client.post(self.location_list_url, data)
>   File "/usr/lib/python3/dist-packages/django/test/client.py", line 543, in 
> post
> response = super().post(path, data=data, content_type=content_type, 
> secure=secure, **extra)
>   File "/usr/lib/python3/dist-packages/django/test/client.py", line 356, in 
> post
> return self.generic('POST', path, post_data, content_type,
>   File "/usr/lib/python3/dist-packages/django/test/client.py", line 422, in 
> generic
> return self.request(**r)
>   File "/usr/lib/python3/dist-packages/django/test/client.py", line 503, in 
> request
> raise exc_value
>   File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", 
> line 34, in inner
> response = get_response(request)
>   File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 
> 115, in _get_response
> response = self.process_exception_by_middleware(e, request)
>   File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 
> 113, in _get_response
> response = wrapped_callback(request, *callback_args, **callback_kwargs)
>   File "/usr/lib/python3/dist-packages/django/views/decorators/csrf.py", line 
> 54, in wrapped_view
> return view_func(*args, **kwargs)
>   File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 
> 71, in view
> return self.dispatch(request, *args, **kwargs)
>   File "/usr/lib/python3/dist-packages/rest_framework/views.py", line 505, in 
> dispatch
> response = self.handle_exception(exc)
>   File "/usr/lib/python3/dist-packages/rest_framework/views.py", line 465, in 
> handle_exception
> self.raise_uncaught_exception(exc)
>   File "/usr/lib/python3/dist-packages/rest_framework/views.py", line 476, in 
> raise_uncaught_exception
> raise exc
>   File "/usr/lib/python3/dist-packages/rest_framework/views.py", line 502, in 
> dispatch
> response = handler(request, *args, **kwargs)
>   File "/usr/lib/python3/dist-packages/rest_framework/generics.py", line 242, 
> in post
> 

Bug#957470: FTBFS Bugs in Debian revdeps dahdi-tools and libpri

[Bernhard Schmidt]

Hi Tzafrir,

> could you have a look at Bug#957117 and #957470? They are causing
> Asterisk to be removed from testing.
> 
> If you currently don't have time to fix this we should probably tag the
> bugs with help and maybe temporarily drop them from the build-deps.

Both bugs are still present (I don't get the FTBFS on mipsel/armel for
dahdi-tools, and libpri has not been fixed yet) and have caused Asterisk
to be removed from testing. Are you planning to work on these? Otherwise
I'd suggest to drop the build-dep to avoid missing some freeze deadline.

Bernhard

Bug#971140: marked as done (rust-lalrpop: FTBFS: build-dependency not installable: librust-itertools-0.8+default-dev)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 11:04:15 -0400
with message-id <87wnzsx30w@fifthhorseman.net>
and subject line Re: Bug#971140: rust-lalrpop: FTBFS: build-dependency not 
installable: librust-itertools-0.8+default-dev
has caused the Debian Bug report #971140,
regarding rust-lalrpop: FTBFS: build-dependency not installable: 
librust-itertools-0.8+default-dev
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.)


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

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, 
> libstd-rust-dev, librust-ascii-canvas-2+default-dev, 
> librust-atty-0.2+default-dev, librust-bit-set-0.5+default-dev, 
> librust-diff-0.1+default-dev (>= 0.1.9-~~), librust-docopt-1+default-dev, 
> librust-ena-0.13+default-dev, librust-itertools-0.8+default-dev, 
> librust-lalrpop-util-0.17+default-dev (>= 0.17.2-~~), 
> librust-petgraph-0.5+default-dev, librust-regex-1+default-dev, 
> librust-regex-syntax-0.6+default-dev, librust-serde-1+default-dev, 
> librust-serde-derive-1+default-dev, librust-sha2-0.8+default-dev, 
> librust-string-cache-0.8+default-dev, librust-term-0.5+default-dev, 
> librust-unicode-xid-0.2+default-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, 
> libstd-rust-dev, librust-ascii-canvas-2+default-dev, 
> librust-atty-0.2+default-dev, librust-bit-set-0.5+default-dev, 
> librust-diff-0.1+default-dev (>= 0.1.9-~~), librust-docopt-1+default-dev, 
> librust-ena-0.13+default-dev, librust-itertools-0.8+default-dev, 
> librust-lalrpop-util-0.17+default-dev (>= 0.17.2-~~), 
> librust-petgraph-0.5+default-dev, librust-regex-1+default-dev, 
> librust-regex-syntax-0.6+default-dev, librust-serde-1+default-dev, 
> librust-serde-derive-1+default-dev, librust-sha2-0.8+default-dev, 
> librust-string-cache-0.8+default-dev, librust-term-0.5+default-dev, 
> librust-unicode-xid-0.2+default-dev, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [558 B]
> Get:5 copy:/<>/apt_archive ./ Packages [643 B]
> Fetched 2164 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librust-itertools-0.8+default-dev 
> but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/09/26/rust-lalrpop_0.17.2-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 ---
Version: 0.17.2-5

On Sun 2020-09-27 20:38:00 +0200, Lucas Nussbaum wrote:
>> The following packages have unmet dependencies:
>>  sbuild-build-depends-main-dummy : Depends: 
>> librust-itertools-0.8+default-dev but it is not installable
>> E: Unable to correct problems, you have held 

Bug#971140: rust-lalrpop: FTBFS: build-dependency not installable: librust-itertools-0.8+default-dev

[Daniel Kahn Gillmor]

Version: 0.17.2-5

On Sun 2020-09-27 20:38:00 +0200, Lucas Nussbaum wrote:
>> The following packages have unmet dependencies:
>>  sbuild-build-depends-main-dummy : Depends: 
>> librust-itertools-0.8+default-dev but it is not installable
>> E: Unable to correct problems, you have held broken packages.
>> apt-get failed.

looks like lalrpop builds and runs fine with itertools 0.9 as well as
0.8.  i've relaxed its build-dependencies for itertools in 0.17.2-5.

At some point, we should move to the latest lalrpop (0.19.1), but that
is going to require at least one round-trip through NEW (lalrpop-util
has a new "lexer" feature), so for now i'm going to just try to get the
existing toolchain to migrate to testing, so that the existing sequoia
packages (and anything else that depends on lalrpop 0.17) can build and
migrate.

--dkg


signature.asc
Description: PGP signature

Bug#957094: marked as done (colmap: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 14:47:19 +
with message-id 
and subject line Bug#957094: fixed in colmap 3.6+really3.6-1
has caused the Debian Bug report #957094,
regarding colmap: 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.)


-- 
957094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:colmap
Version: 3.6+dev2+git20191105-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/colmap_3.6+dev2+git20191105-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

[...]
cd /<>/obj-x86_64-linux-gnu/lib/Graclus && /usr/bin/cc 
-DOPENGL_ENABLED -DOPENMP_ENABLED -I/<>/lib -I/<>/src 
-I/usr/include/eigen3 -I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ 
-I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/<>/lib/Graclus/.  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DDISABLE_CPU_NEON 
-Wno-maybe-uninitialized -fopenmp -w -fPIC   -o 
CMakeFiles/graclus.dir/metisLib/mmd.c.o   -c 
/<>/lib/Graclus/metisLib/mmd.c
[ 20%] Building C object lib/Graclus/CMakeFiles/graclus.dir/metisLib/mpmetis.c.o
cd /<>/obj-x86_64-linux-gnu/lib/Graclus && /usr/bin/cc 
-DOPENGL_ENABLED -DOPENMP_ENABLED -I/<>/lib -I/<>/src 
-I/usr/include/eigen3 -I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ 
-I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/<>/lib/Graclus/.  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DDISABLE_CPU_NEON 
-Wno-maybe-uninitialized -fopenmp -w -fPIC   -o 
CMakeFiles/graclus.dir/metisLib/mpmetis.c.o   -c 
/<>/lib/Graclus/metisLib/mpmetis.c
[ 20%] Building C object lib/Graclus/CMakeFiles/graclus.dir/metisLib/mrefine.c.o
cd /<>/obj-x86_64-linux-gnu/lib/Graclus && /usr/bin/cc 
-DOPENGL_ENABLED -DOPENMP_ENABLED -I/<>/lib -I/<>/src 
-I/usr/include/eigen3 -I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ 
-I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/<>/lib/Graclus/.  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DDISABLE_CPU_NEON 
-Wno-maybe-uninitialized -fopenmp -w -fPIC   -o 
CMakeFiles/graclus.dir/metisLib/mrefine.c.o   -c 
/<>/lib/Graclus/metisLib/mrefine.c
[ 20%] Building C object 
lib/Graclus/CMakeFiles/graclus.dir/metisLib/mrefine2.c.o
cd /<>/obj-x86_64-linux-gnu/lib/Graclus && /usr/bin/cc 
-DOPENGL_ENABLED -DOPENMP_ENABLED -I/<>/lib -I/<>/src 
-I/usr/include/eigen3 -I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ 
-I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/<>/lib/Graclus/.  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 

Bug#971130: marked as pending in djangorestframework-gis

[Michael Fladischer]

Control: tag -1 pending

Hello,

Bug #971130 in djangorestframework-gis reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/djangorestframework-gis/-/commit/95398254a87e46e8f652af8bbba6d3a867d4e084


Upload to unstable (Closes: #971130).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/971130

Processed: Bug#971130 marked as pending in djangorestframework-gis

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #971130 [src:djangorestframework-gis] djangorestframework-gis: FTBFS: 
dh_auto_test: error: pybuild --test -i python{version} -p 3.8 --system=custom 
"--test-args=cd {build_dir}; {interpreter} tests/manage.py test 
tests/django_restframework_gis_tests" returned exit code 13
Added tag(s) pending.

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

Bug#972191: marked as done (cctools ftbfs with python3.9 in unstable)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 13:33:43 +
with message-id 
and subject line Bug#972191: fixed in cctools 7.1.2-2
has caused the Debian Bug report #972191,
regarding cctools ftbfs with python3.9 in unstable
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.)


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

[...]
# make extensions for other supported python versions
if [ -n "3.9" ]; then \
for pyver in 3.9; do \
echo DEBUG ${pyver} ; \
CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong
-Wformat -Werror=format-security -I /usr/include/python3.8 -DNDEBUG
-Wno-unused-result" TWOTOTHREE=/usr/share/doc/python3.8/examples/scripts/2to3
PYTHON3=/usr/bin/python${pyver} ./configure.rerun ; \
make -B -C work_queue/src/bindings/python3 install
CCTOOLS_INSTALL_DIR=/<>/debian/tmp ; \
done ; \
fi
DEBUG 3.9
Linux x86-conova-01 4.19.0-11-amd64 #1 SMP Debian 4.19.146-1 (2020-09-17) x86_64
GNU/Linux
ignoring unknown package /usr
checking for executable gcc.../usr/bin/gcc
checking for GNU make in several places...
checking for executable make.../usr/bin/make
checking if make is GNU make...yes
checking for executable g++.../usr/bin/g++
checking if gcc supports -Wno-unused-parameter...yes
checking if gcc supports -Wno-unknown-pragmas...yes
checking if gcc supports -Wno-deprecated-declarations...yes
checking if gcc supports -Wno-unused-const-variable...yes
checking if ld supports the --as-needed flag...yes
x86_64-linux-gnu
checking for /usr/include/gcc64/globus_common.h...no
checking for /usr/include/globus/globus_common.h...yes
checking for libglobus_gss_assist in /usr/lib...yes
checking for libglobus_gssapi_gsi in /usr/lib...yes
checking for libglobus_gsi_proxy_core in /usr/lib...yes
checking for libglobus_gsi_credential in /usr/lib...yes
checking for libglobus_gsi_callback in /usr/lib...yes
checking for libglobus_oldgaa in /usr/lib...yes
checking for libglobus_gsi_sysconfig in /usr/lib...yes
checking for libglobus_gsi_cert_utils in /usr/lib...yes
checking for libglobus_openssl in /usr/lib...yes
checking for libglobus_openssl_error in /usr/lib...yes
checking for libglobus_callout in /usr/lib...yes
checking for libglobus_proxy_ssl in /usr/lib...yes
checking for libglobus_common in /usr/lib...yes
checking for libltdl in /usr/lib...yes
compiling with globus support
irods support explicitely disabled
checking for libmysqlclient in /usr/lib...yes
compiling with mysql support
xrootd support explicitely disabled
cvmfs support explicitely disabled
uuid support explicitely disabled
checking for libfuse in /usr/lib...yes
compiling with fuse support
checking for libext2fs in /usr/lib...yes
compiling with ext2fs support
checking for executable /usr{,/bin/mpicc,/mpicc}...no
*** Sorry, I couldn't find mpi in /usr
*** Check --with-mpi-path and try again
make[2]: Entering directory '/<>/work_queue/src/bindings/python3'
Makefile:2: /rules.mk: No such file or directory
make[2]: *** No rule to make target '/rules.mk'.  Stop.
make[2]: Leaving directory '/<>/work_queue/src/bindings/python3'
make[1]: *** [debian/rules:30: override_dh_auto_install] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned
exit status 2
--- End Message ---
--- Begin Message ---
Source: cctools
Source-Version: 7.1.2-2
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated cctools 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, 14 Oct 2020 13:56:51 +0100
Source: cctools
Architecture: source
Version: 7.1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair 

Bug#971231: marked as done (golang-github-sjoerdsimons-ostree-go: FTBFS: obj-x86_64-linux-gnu/src/github.com/sjoerdsimons/ostree-go/pkg/otadmin/admin.go:1:1: expected 'package', found 'EOF')

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 13:19:44 +
with message-id 
and subject line Bug#971231: fixed in golang-github-sjoerdsimons-ostree-go 
0.0~git20201014.8fae757-1
has caused the Debian Bug report #971231,
regarding golang-github-sjoerdsimons-ostree-go: FTBFS: 
obj-x86_64-linux-gnu/src/github.com/sjoerdsimons/ostree-go/pkg/otadmin/admin.go:1:1:
 expected 'package', found 'EOF'
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.)


-- 
971231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-sjoerdsimons-ostree-go
Version: 0.0~git20190304.5d29096-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
> obj-x86_64-linux-gnu/src/github.com/sjoerdsimons/ostree-go/pkg/otadmin/admin.go:1:1:
>  expected 'package', found 'EOF'
> obj-x86_64-linux-gnu/src/github.com/sjoerdsimons/ostree-go/pkg/otremote/remoteadd.go:1:1:
>  expected 'package', found 'EOF'
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4
> package .: no Go files in /<>/obj-x86_64-linux-gnu
> dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> returned exit code 1
> make: *** [debian/rules:4: build] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/09/26/golang-github-sjoerdsimons-ostree-go_0.0~git20190304.5d29096-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: golang-github-sjoerdsimons-ostree-go
Source-Version: 0.0~git20201014.8fae757-1
Done: Andrej Shadura 

We believe that the bug you reported is fixed in the latest version of
golang-github-sjoerdsimons-ostree-go, which is due to be installed in the 
Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated 
golang-github-sjoerdsimons-ostree-go 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, 14 Oct 2020 15:07:56 +0200
Source: golang-github-sjoerdsimons-ostree-go
Architecture: source
Version: 0.0~git20201014.8fae757-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Andrej Shadura 
Closes: 971231
Changes:
 golang-github-sjoerdsimons-ostree-go (0.0~git20201014.8fae757-1) unstable; 
urgency=medium
 .
   * New upstream release (Closes: #971231).
   * Bump debhelper from old 10 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Repository, Repository-Browse.
   * Apply multi-arch hints: Add Multi-Arch: foreign.
Checksums-Sha1:
 100fbb8c099ab179235716f6e4ae7895947b919f 2387 
golang-github-sjoerdsimons-ostree-go_0.0~git20201014.8fae757-1.dsc
 cee0f95aa08f33d5aa7c96400c0eb1a915b752c9 17644 
golang-github-sjoerdsimons-ostree-go_0.0~git20201014.8fae757.orig.tar.xz
 cf089f177144432032bb42ddadbccbb20cba9f64 2700 
golang-github-sjoerdsimons-ostree-go_0.0~git20201014.8fae757-1.debian.tar.xz
Checksums-Sha256:
 0a39381b775fd56df6fa247ce2d8fd95123c456149cce1be6b7d9752c38cc46c 2387 
golang-github-sjoerdsimons-ostree-go_0.0~git20201014.8fae757-1.dsc
 0c54272b6492818b78d5df1ffcda1d62c3c6ea590d052163db4cd6948cb4ec80 17644 
golang-github-sjoerdsimons-ostree-go_0.0~git20201014.8fae757.orig.tar.xz
 35610f6ae2cc8082be47d74170c37a12f995b5f94a5dcef4f6644cb619753f7b 2700 
golang-github-sjoerdsimons-ostree-go_0.0~git20201014.8fae757-1.debian.tar.xz

Processed: reassign 972204 to src:kdeconnect, forcibly merging 971736 972204

[Debian Bug Tracking System]

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

> reassign 972204 src:kdeconnect
Bug #972204 [kdeconnect] kdeconnect: CVE-2020-26164
Bug reassigned from package 'kdeconnect' to 'src:kdeconnect'.
No longer marked as found in versions kdeconnect/1.3.3-2.
Ignoring request to alter fixed versions of bug #972204 to the same values 
previously set
> forcemerge 971736 972204
Bug #971736 [src:kdeconnect] kdeconnect: CVE-2020-26164
Bug #972204 [src:kdeconnect] kdeconnect: CVE-2020-26164
Severity set to 'important' from 'grave'
Marked as found in versions kdeconnect/20.04.3-1.
Added tag(s) upstream.
Bug #971736 [src:kdeconnect] kdeconnect: CVE-2020-26164
Added tag(s) patch.
Merged 971736 972204
> thanks
Stopping processing here.

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

Bug#972212: singularity-container: CVE-2020-15229

[Salvatore Bonaccorso]

Source: singularity-container
Version: 3.5.2+ds1-1
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 singularity-container.

CVE-2020-15229[0]:
| Path traversal and files overwrite with unsquashfs

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-15229
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15229
[1] https://github.com/hpcng/singularity/security/advisories/GHSA-7gcp-w6ww-2xv9

Regards,
Salvatore

Processed: tagging 972194

[Debian Bug Tracking System]

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

> tags 972194 + ftbfs
Bug #972194 [src:pyside2] pyside2 is not ready for python3.9
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#972211: FTBFS with OCaml 4.11.1 (-unsafe-string is not available)

[Stéphane Glondu]

Package: src:mldonkey
Version: 3.1.7-2
Severity: serious
Tags: ftbfs

Dear Maintainer,

Your package mldonkey FTBFS with OCaml 4.11.1 because -unsafe-string
is no longer available.


Cheers,

-- 
Stéphane

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

Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Processed: Bug#972194 marked as pending in pyside2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #972194 [src:pyside2] pyside2 is not ready for python3.9
Added tag(s) pending.

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

Bug#972033: python3.9, dask, pandas 1.1

[Rebecca N. Palmer]

Control: severity 969648 serious
Control: tags 969650 pending
Control: tags 972033 pending

Python 3.9 related breakage has been declared RC, so if nobody objects, 
 I intend to upload pandas 1.1 to unstable (possibly tonight, but it 
probably won't build before numpy and matplotlib are binNMUd for Python 
3.9) despite the dask breakage.


As noted in #969648, it is likely that dask can be fixed, but this has 
not been tested in Debian.  (Testing dask also currently fails for lack 
of a Python 3.9 numpy.)

Bug#972194: marked as pending in pyside2

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #972194 in pyside2 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/qt-kde-team/qt/pyside2/-/commit/10d0459b41d0f9e627970f5d297f4edf79264a1b


Backport upstream patch to add support for Python 3.9.

Closes: #972194.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/972194

Bug#972208: python-magcode-core FTBFS: error: failed to run pyversions

[Adrian Bunk]

Source: python-magcode-core
Version: 1.5.4-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=python-magcode-core=all=1.5.4-3=1600816365=0

...
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
dh_auto_clean
dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
dh_auto_clean: warning: Please use the third-party "pybuild" build system 
instead of python-distutils
dh_auto_clean: warning: This feature will be removed in compat 12.
Can't exec "pyversions": No such file or directory at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 124.
dh_auto_clean: error: failed to run pyversions
make[1]: *** [debian/rules:25: override_dh_auto_clean] Error 25

Bug#972209: zsnapd FTBFS: error: failed to run pyversions

[Adrian Bunk]

Source: zsnapd
Version: 0.8.11h-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=zsnapd=all=0.8.11h-3=1600817477=0

...
   dh_auto_clean
dh_auto_clean: warning: Please use the third-party "pybuild" build system 
instead of python-distutils
dh_auto_clean: warning: This feature will be removed in compat 12.
Can't exec "pyversions": No such file or directory at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 124.
dh_auto_clean: error: failed to run pyversions
make: *** [debian/rules:14: clean] Error 25

Bug#972207: pymongo ftbfs with python3.9 as supported python3 version

[Matthias Klose]

Package: src:pymongo
Version: 3.10.0-2
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9


==
FAIL: test_instantiation (test_custom_types.TestBSONTypeEnDeCodecs)
--
TypeError: Can't instantiate abstract class testcodec with abstract method
transform_python

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/<>/test/test_custom_types.py", line 270, in 
test_instantiation
run_test(TypeEncoder, {'python_type': MyType,}, fail=True)
  File "/<>/test/test_custom_types.py", line 263, in run_test
codec()
AssertionError: "Can't instantiate abstract class .* with abstract methods .*"
does not match "Can't instantiate abstract class testcodec with abstract method
transform_python"

--
Ran 317 tests in 5.721s

FAILED (failures=1, skipped=125)
E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1:
python3.9 setup.py test
dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned
exit code 13
make: *** [debian/rules:8: build-arch] Error 25
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Build finished at 2020-10-14T02:40:37Z

Finished

Bug#972206: remctl ftbfs in unstable (failing tests)

[Matthias Klose]

Package: src:remctl
Version: 4.16-3
Severity: serious
Tags: sid bullseye

https://buildd.debian.org/status/fetch.php?pkg=remctl=amd64=3.16-4%2Bb7=1602646591=0

[...]
make  check-local
make[2]: Entering directory '/<>'
tests/runtests -l '/<>/tests/TESTS'

Running all tests listed in TESTS.  If any tests fail, run the failing
test program with runtests -o to see more details.

client/api..skipped (Kerberos tests not configured)
client/ccache...skipped (Kerberos tests not configured)
client/largeskipped (Kerberos tests not configured)
client/open.ok (skipped 15 tests)
client/remctl...skipped (Kerberos tests not configured)
client/source-ipskipped (Kerberos tests not configured)
client/timeout..skipped (Kerberos tests not configured)
docs/podskipped (POD syntax tests normally skipped)
docs/pod-spelling...skipped (Spelling tests only run for author)
docs/spdx-license...skipped (SPDX identifier tests normally skipped)
perl/module-version.skipped (Module version tests normally skipped)
portable/asprintf...ok
portable/daemon.ok
portable/getaddrinfook
portable/getnameinfook
portable/getopt.ok
portable/inet_aton..ok
portable/inet_ntoa..ok
portable/inet_ntop..ok
portable/mkstempok
portable/setenv.ok
portable/snprintf...ok
server/accept...skipped (Kerberos tests not configured)
server/acl..ok (skipped 4 tests)
server/acl/localgroup...ok
server/anonymousskipped (Kerberos tests not configured)
server/bind.skipped (Kerberos tests not configured)
server/config...ok
server/continue.skipped (Kerberos tests not configured)
server/emptyskipped (Kerberos tests not configured)
server/env..skipped (Kerberos tests not configured)
server/errors...skipped (Kerberos tests not configured)
server/help.skipped (Kerberos tests not configured)
server/invalid..skipped (Kerberos tests not configured)
server/logging..ok
server/misc.skipped (Kerberos tests not configured)
server/shell-misc...ok
server/ssh-parseok
server/stdinskipped (Kerberos tests not configured)
server/streamingskipped (Kerberos tests not configured)
server/sudo.ok
server/summary..skipped (Kerberos tests not configured)
server/user.skipped (Kerberos tests not configured)
server/version..skipped (Kerberos tests not configured)
style/obsolete-strings..skipped (Obsolete strings tests only run for author)
util/buffer.ok
util/gss-tokens.skipped (Kerberos tests not configured)
util/messages...ok
util/messages-krb5..ok
util/network/addr-ipv4..ok
util/network/addr-ipv6..ok
util/network/client.ok
util/network/server.MISSED 34-42 (killed by signal 14)
util/tokens.ok
util/vector.ok
util/xmallocskipped (xmalloc tests only run for author)
util/xwrite.ok (skipped 2 tests)
valgrind/logs...skipped (Not testing under valgrind)

Failed Set Fail/Total (%) Skip Stat  Failing Tests
-- --    
util/network/server   9/3426%8   --  34-42

Failed 9/1998 tests, 99.55% okay, 58 tests skipped.
Files=58,  Tests=1998,  16.15 seconds (1.09 usr + 0.33 sys = 1.42 CPU)
make[2]: *** [Makefile:4628: check-local] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:3986: check-am] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:26: binary-arch] Error 25

Bug#972205: arm-compute-library binary-all FTBFS: This package can only be built for armhf and arm64

[Adrian Bunk]

Source: arm-compute-library
Version: 19.11-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=arm-compute-library=all=19.11-2=1600652275=0

...
   dh_clean
Unknown architecture amd64
This package can only be built for armhf and arm64
exit 1
make: *** [debian/rules:14: clean] Error 1


The binary-all buildds are amd64.

Bug#972204: kdeconnect: CVE-2020-26164

[Adi Kriegisch]

Package: kdeconnect
Version: 1.3.3-2
Severity: grave
Tags: security, patch

Dear maintainers,

on the oss-security mailing list[1], severe bugs in kdeconnect were
published with links to commits that fix them. Find attached backports of
those patches fitting the version of kdeconnect in debian/stable (buster).

Please have a careful look at CVE-2020-26164_g_ssl_validation_checks.patch
and check, whether those two disconnect() calls should really be disabled;
while testing the patches I could not find any adverse effects.

best regards,
Adi Kriegisch

[1] https://www.openwall.com/lists/oss-security/2020/10/13/4
From b279c52101d3f7cc30a26086d58de0b5f1c547fa Mon Sep 17 00:00:00 2001
From: Albert Vaca Cintora 
Date: Thu, 24 Sep 2020 17:01:03 +0200
Subject: [PATCH] Do not leak the local user in the device name.

Thanks Matthias Gerstner  for reporting this.
---
 core/kdeconnectconfig.cpp | 8 +---
 1 file changed, 1 insertion(+), 1 deletions(-)

--- a/core/kdeconnectconfig.cpp	2020-10-14 08:57:39.290290968 +0200
+++ b/core/kdeconnectconfig.cpp	2020-10-14 08:57:57.650342491 +0200
@@ -148,7 +148,7 @@
 
 QString KdeConnectConfig::name()
 {
-QString defaultName = qgetenv("USER") + '@' + QHostInfo::localHostName();
+QString defaultName = QHostInfo::localHostName();
 QString name = d->m_config->value(QStringLiteral("name"), defaultName).toString();
 return name;
 }
From d35b88c1b25fe13715f9170f18674d476ca9acdc Mon Sep 17 00:00:00 2001
From: Matthias Gerstner 
Date: Thu, 24 Sep 2020 17:03:06 +0200
Subject: [PATCH] Fix use after free in LanLinkProvider::connectError()

If QSslSocket::connectToHost() hasn't finished running.

Thanks Matthias Gerstner  for reporting this.
---
 core/backends/lan/lanlinkprovider.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: kdeconnect-1.3.3/core/backends/lan/lanlinkprovider.cpp
===
--- kdeconnect-1.3.3.orig/core/backends/lan/lanlinkprovider.cpp
+++ kdeconnect-1.3.3/core/backends/lan/lanlinkprovider.cpp
@@ -224,7 +224,7 @@ void LanLinkProvider::connectError()
 //The socket we created didn't work, and we didn't manage
 //to create a LanDeviceLink from it, deleting everything.
 delete m_receivedIdentityPackets.take(socket).np;
-delete socket;
+socket->deleteLater();
 }
 
 //We received a UDP packet and answered by connecting to them by TCP. This gets called on a succesful connection.
From 721ba9faafb79aac73973410ee1dd3624ded97a5 Mon Sep 17 00:00:00 2001
From: Aleix Pol 
Date: Wed, 16 Sep 2020 02:27:13 +0200
Subject: [PATCH] Don't brute-force reading the socket

The package will arrive eventually, and dataReceived will be emitted.
Otherwise we just end up calling dataReceived to no end.

Thanks Matthias Gerstner  for reporting this.
---
 core/backends/lan/socketlinereader.cpp |  8 ---
 tests/testsocketlinereader.cpp | 31 --
 2 files changed, 29 insertions(+), 10 deletions(-)

Index: kdeconnect-1.3.3/core/backends/lan/socketlinereader.cpp
===
--- kdeconnect-1.3.3.orig/core/backends/lan/socketlinereader.cpp
+++ kdeconnect-1.3.3/core/backends/lan/socketlinereader.cpp
@@ -38,14 +38,6 @@ void SocketLineReader::dataReceived()
 }
 }
 
-//If we still have things to read from the socket, call dataReceived again
-//We do this manually because we do not trust readyRead to be emitted again
-//So we call this method again just in case.
-if (m_socket->bytesAvailable() > 0) {
-QMetaObject::invokeMethod(this, "dataReceived", Qt::QueuedConnection);
-return;
-}
-
 //If we have any packets, tell it to the world.
 if (!m_packets.isEmpty()) {
 Q_EMIT readyRead();
Index: kdeconnect-1.3.3/tests/testsocketlinereader.cpp
===
--- kdeconnect-1.3.3.orig/tests/testsocketlinereader.cpp
+++ kdeconnect-1.3.3/tests/testsocketlinereader.cpp
@@ -24,16 +24,19 @@
 #include 
 #include 
 #include 
+#include 
 
 class TestSocketLineReader : public QObject
 {
 Q_OBJECT
 public Q_SLOTS:
-void initTestCase();
+void init();
+void cleanup() { delete m_server; }
 void newPacket();
 
 private Q_SLOTS:
 void socketLineReader();
+void badData();
 
 private:
 QTimer m_timer;
@@ -44,8 +47,9 @@ private:
 SocketLineReader* m_reader;
 };
 
-void TestSocketLineReader::initTestCase()
+void TestSocketLineReader::init()
 {
+m_packets.clear();
 m_server = new Server(this);
 
 QVERIFY2(m_server->listen(QHostAddress::LocalHost, 8694), "Failed to create local tcp server");
@@ -96,6 +100,29 @@ void TestSocketLineReader::socketLineRea
 }
 }
 
+void TestSocketLineReader::badData()
+{
+const QList dataToSend = { "data1\n", "data" }; //does not end in a \n
+for (const QByteArray& line : qAsConst(dataToSend)) {
+m_conn->write(line);
+}
+

Bug#957449: marked as done (libkolabxml: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 10:34:02 +
with message-id 
and subject line Bug#957449: fixed in libkolabxml 1.1.6-7
has caused the Debian Bug report #957449,
regarding libkolabxml: 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.)


-- 
957449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libkolabxml
Version: 1.1.6-6
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/libkolabxml_1.1.6-6_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

[...]
+ _ZNSt8auto_ptrIN9vcard_4_012notePropTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_012notePropTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_013TimeStampTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_013TimeStampTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_013TypeValueTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_013TypeValueTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_013emailPropTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_013emailPropTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_013fburlPropTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_013fburlPropTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_013photoPropTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_013photoPropTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_013titlePropTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_013titlePropTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_014genderPropTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_014genderPropTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_014memberPropTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_014memberPropTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_014prodidPropTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_014prodidPropTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_015UriPropertyTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_015UriPropertyTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_015relatedPropTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_015relatedPropTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_016TextPropertyTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_016TextPropertyTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_016nicknamePropTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_016nicknamePropTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_017ArrayOfParametersEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_017ArrayOfParametersEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_017BaseParameterTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_017BaseParameterTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_017PrefTypeValueTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_017PrefTypeValueTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_018categoriesPropTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_018categoriesPropTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_019CryptoTypeValueTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_019CryptoTypeValueTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_019affiliationPropTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_019affiliationPropTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_019anniversaryPropTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_019anniversaryPropTypeEED2Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_028NonEmptyTextListPropertyTypeEED1Ev@Base 1.1.6-6
+ _ZNSt8auto_ptrIN9vcard_4_028NonEmptyTextListPropertyTypeEED2Ev@Base 1.1.6-6
+ 

Processed: severity of 948197 is grave

[Debian Bug Tracking System]

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

> severity 948197 grave
Bug #948197 [src:gthumb] gthumb: CVE-2019-20326: Heap buffer overflow
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#919348: xfce4-screensaver: Accidental upload to unstable while fixing bug #919151

[Enrique]

Package: xfce4-screensaver
Followup-For: Bug #919348

Hi,

is there a chance that xfce4-screensaver makes it into bullseye? I see that
0.1.10 is in unstable. Do you know if that version would work with current
XFCE4 in bullseye?



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

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

Bug#972013: marked as done (mypy ftbfs with python3.9)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 09:07:05 +
with message-id 
and subject line Bug#972013: fixed in mypy 0.790-1
has caused the Debian Bug report #972013,
regarding mypy ftbfs with python3.9
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.)


-- 
972013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mypy
Version: 0.782-1
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

[...]
The manual pages are in debian.
MYPY_USE_MYPYC=1 dh_auto_build
pybuild --build -i python{version} -p "3.9 3.8"
I: pybuild base:217: /usr/bin/python3.9 setup.py build
Parsed and typechecked in 52.560s
Compiled to C in 0.000s
mypy/fastparse.py:1255: error: "ExtSlice" has no attribute "dims"
mypy/fastparse.py:1259: error: "Index" has no attribute "value"
E: pybuild pybuild:352: build: plugin distutils failed with: exit code=1:
/usr/bin/python3.9 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p "3.9 3.8" returned
exit code 13
make[1]: *** [debian/rules:49: override_dh_auto_build] Error 25
--- End Message ---
--- Begin Message ---
Source: mypy
Source-Version: 0.790-1
Done: cru...@debian.org (Michael R. Crusoe)

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated mypy 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, 14 Oct 2020 10:33:35 +0200
Source: mypy
Architecture: source
Version: 0.790-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 972013
Changes:
 mypy (0.790-1) unstable; urgency=medium
 .
   * New upstream version
   * debian/patches/ignore_mypyc: refreshed
   * debian/patches/mypyc_analysis: add files accidently left out of upstream's
 tarball
 Closes: #972013
   * Disable self test until pytest >= 6.0 is in Debian
Checksums-Sha1:
 e10a10fe53f1d237361a4442d875bce09c5065ac 2498 mypy_0.790-1.dsc
 51ab5882129d37672be937a7631a29fe29686432 2587141 mypy_0.790.orig.tar.gz
 659bbf3a05726997477197bb7c0681fd9c8f41cd 16980 mypy_0.790-1.debian.tar.xz
 88e09082f688c5be855b2bf37a5cfda719eee6bc 8576 mypy_0.790-1_source.buildinfo
Checksums-Sha256:
 94aa21d82aa67c92934602220b62e680baf3d7b0bb7dda221fdfd09537e580c5 2498 
mypy_0.790-1.dsc
 2b21ba45ad9ef2e2eb88ce4aeadd0112d0f5026418324176fd494a6824b74975 2587141 
mypy_0.790.orig.tar.gz
 b03ab78b5afbd8356421454eca1b63fba015f7ca993a14cd6ef83e9611b43c12 16980 
mypy_0.790-1.debian.tar.xz
 0953a648dde036c99c64d18c37c99cb1155715c1bfdf2426ccbeebda7b95435f 8576 
mypy_0.790-1_source.buildinfo
Files:
 15382e107ac6c1118f1ee9a39f16e04d 2498 utils optional mypy_0.790-1.dsc
 2e92a8ce0ff0dfc9cee059b4fcccdfc4 2587141 utils optional mypy_0.790.orig.tar.gz
 da7fbb7afd0fd48a7b86ddbfad60ab37 16980 utils optional 
mypy_0.790-1.debian.tar.xz
 9d7e22f4909ca20a7e231dd1345be1f2 8576 utils optional 
mypy_0.790-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl+Gt/wACgkQPCZ2P2xn
5uJKmhAAtV/vnsoGlfsDqChHmybBbXrtXtji+cqw/AWKXMxeb99DqS0VWqSVztkj
C7jPe4ZgW3t/YVDc3rtc/GNBK96KJAq+X1MbRp+asjuiUNOfeNUFbNbUmd5OXwSI
dxOtxLdwR7hwCYn7gPCmCQgTav7FDMtyavN2YYO5thwPIFE6IcMF7dLh2P4XrCZv
ZpxATjaaQ+bpCnmJ6Ni+hoa3nw/Zor5PpLBnVLlgPwJmblFWAr9hWsa+T76z9fqe
w93OpWRvaCHZy89eGU5bJOI+4EuZ31JZyAMge7L2O3VklptogcbPC4tWIND5r6TN
V7pUdN+lWbzAe5MTj9uLUvNqTZcXNTyWS54UY+u3aOZFAc2Sp2C0mnbKRwroQPfX
hrTKtJurYHrb6Tx81dvt2dFUyCoyl11a3gUSowCY8RSvoC3cG0/NFYNn6x4ny+LO
jUl7s65gAw14FGBJr18RsAJR/yZBOb1xkt3AI37qNXsaMPeRbHVPPZm7kV+F5kyW
OZt86jTD8dPTauUpYZBqsxcvEwobE86zmOZyEFMlBHH78FFuwPmkT7KY3dBF0vF1
HNFbV4TSwMaxeMOE7TAMSIceqwrOkjWZHZlhDylKlZJJjaSoHLRz/s6F1akM+1KB
HuXXVCLNzOMJriyxuZ5ZrAblQGTUhZwlAUcw8273Ke9jbdzLLAA=
=o/1O
-END PGP SIGNATURE End Message ---

Processed: reassign 972145 to libmalcontent-0-0

[Debian Bug Tracking System]

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

> reassign 972145 libmalcontent-0-0
Bug #972145 [flatpak] mct_manager_get_app_filter() fails closed if 
accountsservice not installed
Bug reassigned from package 'flatpak' to 'libmalcontent-0-0'.
No longer marked as found in versions flatpak/1.8.2-2.
Ignoring request to alter fixed versions of bug #972145 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#972195: python-setproctitle's tests fail in unstable

[Matthias Klose]

Package: src:python-setproctitle
Version: 1.1.10-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9


python-setproctitle's tests fail in unstable.

[...]
==
FAIL: No problem with encoded argv[0] path.
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.8_setproctitle/build/tests/setproctitle_test.py",
line 272, in test_weird_path
rv = self.run_script(r"""
  File
"/<>/.pybuild/cpython3_3.8_setproctitle/build/tests/setproctitle_test.py",
line 416, in run_script
self.fail("test script failed")
AssertionError: test script failed
 >> begin captured stdout << -
b''
b'/bin/sh: 1: /tmp/tmp5aaqs7oa/u20ac/u2603/python: not found\n'

- >> end captured stdout << --

[...]
==
FAIL: Title can contain unicode characters.
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.8_setproctitle/build/tests/setproctitle_test.py",
line 230, in test_unicode
self.fail("unexpected ps output: %r" % title)
AssertionError: unexpected ps output: 'Hello, ☃!'

Bug#972194: pyside2 is not ready for python3.9

[Matthias Klose]

Package: src:pyside2
Version: 5.15.0-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

pyside2 is not ready for python3.9:

[...]
dpkg-buildpackage: info: host architecture amd64
dpkg-source: info: using options from pyside2-5.15.0/debian/source/options:
--extend-diff-ignore=^[^/]*[.]egg-info/
 debian/rules clean
dh clean --with python3,sphinxdoc --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.9 setup.py clean
Unsupported python version detected. Only these python versions are supported:
[(2, 7), (3, 5), (3, 6), (3, 7), (3, 8)]
E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1:
python3.9 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.9 3.8" returned
exit code 13
make: *** [debian/rules:30: clean] Error 25

Bug#972009: gudhi ftbfs with python3.9 as supported python version

[Gard Spreemann]

Matthias Klose  writes:

> Package: src:gudhi
> Version: 3.3.0+dfsg-1
> Severity: important
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: python3.9
>
> seem to be a packaging error

Indeed! Thanks for reporting. I think I know what's wrong, and will get
to it soon.

Bug#971788: Any workaround?

[Atamert Ölçgen]

I am having the same problem. Unable to upgrade nvidia-rtcore because of
this missing package.

Does this package require gcc-10? (or was it because the next release will
be based on gcc-10?)

Is there any workaround? (short of switching to buster)

-- 
Kind Regards,
Atamert Ölçgen

◻◼◻
◻◻◼
◼◼◼

www.muhuk.com

Bug#972191: cctools ftbfs with python3.9 in unstable

[Matthias Klose]

Package: src:cctools
Version: 7.1.2-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

[...]
# make extensions for other supported python versions
if [ -n "3.9" ]; then \
for pyver in 3.9; do \
echo DEBUG ${pyver} ; \
CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong
-Wformat -Werror=format-security -I /usr/include/python3.8 -DNDEBUG
-Wno-unused-result" TWOTOTHREE=/usr/share/doc/python3.8/examples/scripts/2to3
PYTHON3=/usr/bin/python${pyver} ./configure.rerun ; \
make -B -C work_queue/src/bindings/python3 install
CCTOOLS_INSTALL_DIR=/<>/debian/tmp ; \
done ; \
fi
DEBUG 3.9
Linux x86-conova-01 4.19.0-11-amd64 #1 SMP Debian 4.19.146-1 (2020-09-17) x86_64
GNU/Linux
ignoring unknown package /usr
checking for executable gcc.../usr/bin/gcc
checking for GNU make in several places...
checking for executable make.../usr/bin/make
checking if make is GNU make...yes
checking for executable g++.../usr/bin/g++
checking if gcc supports -Wno-unused-parameter...yes
checking if gcc supports -Wno-unknown-pragmas...yes
checking if gcc supports -Wno-deprecated-declarations...yes
checking if gcc supports -Wno-unused-const-variable...yes
checking if ld supports the --as-needed flag...yes
x86_64-linux-gnu
checking for /usr/include/gcc64/globus_common.h...no
checking for /usr/include/globus/globus_common.h...yes
checking for libglobus_gss_assist in /usr/lib...yes
checking for libglobus_gssapi_gsi in /usr/lib...yes
checking for libglobus_gsi_proxy_core in /usr/lib...yes
checking for libglobus_gsi_credential in /usr/lib...yes
checking for libglobus_gsi_callback in /usr/lib...yes
checking for libglobus_oldgaa in /usr/lib...yes
checking for libglobus_gsi_sysconfig in /usr/lib...yes
checking for libglobus_gsi_cert_utils in /usr/lib...yes
checking for libglobus_openssl in /usr/lib...yes
checking for libglobus_openssl_error in /usr/lib...yes
checking for libglobus_callout in /usr/lib...yes
checking for libglobus_proxy_ssl in /usr/lib...yes
checking for libglobus_common in /usr/lib...yes
checking for libltdl in /usr/lib...yes
compiling with globus support
irods support explicitely disabled
checking for libmysqlclient in /usr/lib...yes
compiling with mysql support
xrootd support explicitely disabled
cvmfs support explicitely disabled
uuid support explicitely disabled
checking for libfuse in /usr/lib...yes
compiling with fuse support
checking for libext2fs in /usr/lib...yes
compiling with ext2fs support
checking for executable /usr{,/bin/mpicc,/mpicc}...no
*** Sorry, I couldn't find mpi in /usr
*** Check --with-mpi-path and try again
make[2]: Entering directory '/<>/work_queue/src/bindings/python3'
Makefile:2: /rules.mk: No such file or directory
make[2]: *** No rule to make target '/rules.mk'.  Stop.
make[2]: Leaving directory '/<>/work_queue/src/bindings/python3'
make[1]: *** [debian/rules:30: override_dh_auto_install] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned
exit status 2

Bug#775147: marked as done (emscripten: does not work at all with optimization enabled)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 09:49:44 +0200
with message-id <160266178482.3150661.1223129177875...@auryn.jones.dk>
and subject line Re: emscripten: does not work at all with optimization enabled
has caused the Debian Bug report #775147,
regarding emscripten: does not work at all with optimization enabled
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.)


-- 
775147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emscripten
Version: 1.22.1-1
Severity: grave
Justification: renders package almost completely unusable

I cannot seem to get emscripten to compile anything with -O1 or -O2 or
-O3 (specifying -O0 or no -O option appears to work for simple examples,
but possibly not for more complex code, see below). I hope I am not
doing something completely wrong, since this is my first time using
emscripten...


For example, even the simplest code I could think of fails:

$ echo 'int main() { return 0; }' >foo.c
$ rm -r ~/.emscripten* /tmp/emscripten_temp* ; emcc ; EMCC_DEBUG=1 emcc -O2 -o 
foo.html foo.c
[... lots of output snipped, full output in attached output-1.txt.gz ...]
INFO root: ===
INFO root: bootstrapping relooper...
INFO root:   bootstrap phase 1
WARNING  root: LLVM version appears incorrect (seeing "3.5.0-9", expected "3.4")
INFO root: (Emscripten: Running sanity checks)
clang: warning: argument unused during compilation: '-nostdinc++'
Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/multiprocessing/pool.py", line 380, in _handle_result
s  
task = get()
TypeError: ('__init__() takes at least 3 arguments (1 given)', , ())

... and then it hangs waiting for something until I abort it with
Ctrl-C. After that, amid a few Python stack traces, it outputs:

ERRORroot: bootstrapping relooper failed. You may need to manually create re
looper.js by compiling it, see src/relooper/emscripten 


Because of the LLVM version warning above, I also installed the
packages clang-3.4 and llvm-3.4 and tried to use those versions by
setting LLVM_ROOT like this:

$ rm -r ~/.emscripten* /tmp/emscripten_temp* ; emcc ; sed -i "s,^LLVM_ROOT 
=.*,LLVM_ROOT = '/usr/lib/llvm-3.4/bin'," ~/.emscripten ; EMCC_DEBUG=1 emcc -O2 
-o foo.html foo.c

but it hanged in the same way (full output in attached output-2.txt.gz).
(I couldn't just remove llvm-3.5 and clang-3.5 entirely, since the
emscripten package depends on clang which currently depends on
clang-3.5. If the version really matters in some cases, perhaps
emscripten should depend on a specific LLVM version and use it by
default?)


Without optimizations, the compilation works:

$ rm -r ~/.emscripten* /tmp/emscripten_temp* ; emcc ; EMCC_DEBUG=1 emcc -o 
foo.html foo.c
[... full output in attached output-3.txt.gz ...]
DEBUGroot: generating HTML
DEBUGroot: emcc step "final emitting" took 0.18 seconds
DEBUGroot: total time: 17.98 seconds

The options -O1 and -O3 do not work either, but -O0 works. Compiling
some other small tests from /usr/share/emscripten/tests (e.g.
files.cpp) fails in the same way.

Using separate compilation (emcc -O2 -c foo.c ; emcc -O2 -o foo.html
foo.o) also fails in the same way. However, specifying -O0 to the link
command (emcc -O2 -c foo.c ; emcc -O0 -o foo.html foo.o) seems to work
at least for this simple example.

Even without optimizations, I am not sure if emscripten works for more
complex code: I originally ran into this bug trying to compile SDL 2
(upstream Mercurial version, commenting out a few lines because Debian's
emscripten is too old for some functions that it uses) and an SDL-using
application. I then tried inserting CFLAGS=-O0 for the configure script
of SDL and the Makefile of my application, but ran into the same bug
anyway. However, I guess it's possible that one file somewhere got
compiled with optimizations, since the build process is quite complex.
The command that failed (the very last link command, the only one with
-o something.html) did have -O0, and it still failed.

In any case, this bug does appear to make real-world use of Debian's
current emscripten package at least very difficult if 

Processed: Re: python3.9, dask, pandas 1.1

[Debian Bug Tracking System]

Processing control commands:

> severity 969648 serious
Bug #969648 [python3-dask] dask: autopkgtest fail with pandas 1.1 - datetime 
issues
Severity set to 'serious' from 'normal'
> tags 969650 pending
Bug #969650 [python3-pandas] transition: pandas 1.0 -> 1.1
Added tag(s) pending.
> tags 972033 pending
Bug #972033 [src:pandas] pandas ftbfs with python3.9 as supported python version
Bug #972015 [src:pandas] pandas ftbfs with python3 as supported python version
Added tag(s) pending.
Added tag(s) pending.

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

Processed: Re: python3.9, dask, pandas 1.1

[Debian Bug Tracking System]

Processing control commands:

> severity 969648 serious
Bug #969648 [python3-dask] dask: autopkgtest fail with pandas 1.1 - datetime 
issues
Ignoring request to change severity of Bug 969648 to the same value.
> tags 969650 pending
Bug #969650 [python3-pandas] transition: pandas 1.0 -> 1.1
Ignoring request to alter tags of bug #969650 to the same tags previously set
> tags 972033 pending
Bug #972033 [src:pandas] pandas ftbfs with python3.9 as supported python version
Bug #972015 [src:pandas] pandas ftbfs with python3 as supported python version
Ignoring request to alter tags of bug #972033 to the same tags previously set
Ignoring request to alter tags of bug #972015 to the same tags previously set

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

Processed: Re: python3.9, dask, pandas 1.1

[Debian Bug Tracking System]

Processing control commands:

> severity 969648 serious
Bug #969648 [python3-dask] dask: autopkgtest fail with pandas 1.1 - datetime 
issues
Ignoring request to change severity of Bug 969648 to the same value.
> tags 969650 pending
Bug #969650 [python3-pandas] transition: pandas 1.0 -> 1.1
Ignoring request to alter tags of bug #969650 to the same tags previously set
> tags 972033 pending
Bug #972033 [src:pandas] pandas ftbfs with python3.9 as supported python version
Bug #972015 [src:pandas] pandas ftbfs with python3 as supported python version
Ignoring request to alter tags of bug #972033 to the same tags previously set
Ignoring request to alter tags of bug #972015 to the same tags previously set

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

Bug#971949: marked as done (pitivi: missing dependency on gir1.2-gst-plugins-bad-1.0)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 07:35:29 +
with message-id 
and subject line Bug#971949: fixed in pitivi 2020.09.1-1
has caused the Debian Bug report #971949,
regarding pitivi: missing dependency on gir1.2-gst-plugins-bad-1.0
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.)


-- 
971949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pitivi
Version: 2020.09-1
Severity: serious
Justification: Policy 3.5

Dear Maintainer,

After the upgrade to 2020.09-1, pitivi fails to start. I tried first via
the GNOME UI, and nothing happened. Then I tried on a terminal, and got
this:

~$ pitivi
Não foi possível importar “GstTranscoder”. Certifique-se de que ele está 
disponível.

That's pt_BR for `Impossible to import "GstTranscoder". Make sure it's
available'`, but for some reason even setting LANG=C doesn't get me the
message in English).

Installing gir1.2-gst-plugins-bad-1.0 makes pitivi start. I have not
tested it on a clean system to see if there are any other missing
dependencies.

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

Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pitivi depends on:
ii  gir1.2-gdkpixbuf-2.02.40.0+dfsg-5
ii  gir1.2-ges-1.0  1.18.0-2
ii  gir1.2-glib-2.0 1.66.0-1
ii  gir1.2-gst-plugins-base-1.0 1.18.0-2
ii  gir1.2-gstreamer-1.01.18.0-3
ii  gir1.2-gtk-3.0  3.24.23-2
ii  gir1.2-pango-1.01.46.2-1
pn  gstreamer1.0-audiosink  
ii  gstreamer1.0-gl [gstreamer1.0-videosink]1.18.0-2
ii  gstreamer1.0-gtk3 [gstreamer1.0-videosink]  1.18.0-1
ii  gstreamer1.0-plugins-bad [gstreamer1.0-videosink]   1.18.0-2+b1
ii  gstreamer1.0-plugins-base   1.18.0-2
ii  gstreamer1.0-plugins-good [gstreamer1.0-videosink]  1.18.0-1
ii  gstreamer1.0-x [gstreamer1.0-videosink] 1.18.0-2
ii  libc6   2.31-3
ii  libcairo2   1.16.0-4
ii  libglib2.0-02.66.0-2
ii  libgstreamer1.0-0   1.18.0-3
ii  libpython3.83.8.6-1
ii  python3 3.8.2-3
ii  python3-cairo   1.16.2-4
ii  python3-dbus1.2.16-3
ii  python3-gi  3.38.0-1
ii  python3-gi-cairo3.38.0-1
ii  python3-gst-1.0 1.18.0-1
ii  python3-matplotlib  3.3.2-1
ii  python3-numpy   1:1.19.2-2
ii  python3-xdg 0.26-3
ii  python3.8   3.8.6-1

pitivi recommends no packages.

Versions of packages pitivi suggests:
pn  frei0r-plugins 
ii  gir1.2-gnomedesktop-3.03.38.1-1
pn  gir1.2-gsound-1.0  
ii  gir1.2-notify-0.7  0.7.9-1
ii  gstreamer1.0-libav 1.18.0-1
ii  gstreamer1.0-plugins-ugly  1.18.0-1

-- no debconf information


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: pitivi
Source-Version: 2020.09.1-1
Done: =?utf-8?q?Sebastian_Dr=C3=B6ge?= 

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

Debian distribution maintenance software
pp.
Sebastian Dröge  (supplier of updated pitivi package)

(This message was generated automatically at their request; if you

Bug#972022: marked as done (python-dmicode ftbfs with python3.9 as supported python version)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 07:19:01 +
with message-id 
and subject line Bug#972022: fixed in libxml2 2.9.10+dfsg-6.1
has caused the Debian Bug report #972022,
regarding python-dmicode ftbfs with python3.9 as supported python version
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.)


-- 
972022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-dmicode
Version: 3.12.2-11
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

[...]
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
set -e ;\
for python in python3.9 python3.8; do \
/usr/bin/make PY_BIN=$python -C unit-tests test; \
#/usr/bin/make PY_BIN=$python-dbg -C unit-tests test; \
done
make[2]: Entering directory '/<>/unit-tests'
python3.9 unit -vv

 * Testing for command line version of dmidecode ...WARN
 * Running test as normal user, some tests will be skipped
 * Creation of temporary files...PASS

 * Importing module...FAIL
No module named 'libxml2mod'

make[2]: *** [Makefile:4: test] Error 1
make[2]: Leaving directory '/<>/unit-tests'
make[1]: *** [debian/rules:31: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
--- End Message ---
--- Begin Message ---
Source: libxml2
Source-Version: 2.9.10+dfsg-6.1
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libxml2 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, 14 Oct 2020 08:45:25 +0200
Source: libxml2
Architecture: source
Version: 2.9.10+dfsg-6.1
Distribution: unstable
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: Matthias Klose 
Closes: 972022
Changes:
 libxml2 (2.9.10+dfsg-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build with Python 3.9. Closes: #972022.
Checksums-Sha1:
 8bc389aeb8c0ca972d0be0ff0b597e2e4806b337 2713 libxml2_2.9.10+dfsg-6.1.dsc
 37891793f5945033306b2c77196c96f0c56403db 29500 
libxml2_2.9.10+dfsg-6.1.debian.tar.xz
 0445621d8d266f7ff0e4f72a168d733a4a4e4369 5848 
libxml2_2.9.10+dfsg-6.1_source.buildinfo
Checksums-Sha256:
 1d826b22548308f5f5cd3136f3416d3d1b94d16dd5e83477b6b644607b288db6 2713 
libxml2_2.9.10+dfsg-6.1.dsc
 dff5f7823256590666bfeffabe9b3afd35fa4b4b7b8e9253827281da286b42f8 29500 
libxml2_2.9.10+dfsg-6.1.debian.tar.xz
 e93a74591445e2b10b53b1ae9733b2fbe05a3782d131d7b7fa5c2105f2bdab81 5848 
libxml2_2.9.10+dfsg-6.1_source.buildinfo
Files:
 eff3198d279ad1937162ddfe216072c3 2713 libs optional libxml2_2.9.10+dfsg-6.1.dsc
 19fda762dfd95d166d072d17e83de5a9 29500 libs optional 
libxml2_2.9.10+dfsg-6.1.debian.tar.xz
 66c88eddf5e769ccf4a1c281926e8157 5848 libs optional 
libxml2_2.9.10+dfsg-6.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl+Gn9oQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9YTjEACvuI49JkZJ9CJ4NmeqTVsGI7djSfYuXu0f
UazDcEb+nu32pJmHXtNBPOPyr7G9Z3C8kJELbzEvmW65wgd/WQCae9fe2eTOhMoj
wWn2Q34pB7A0L4iEFQwqIFTYHAyPYGZNN3dFZns7tljzFuc/CQ+dqvkLT+/Ymu6V
7/AwqAwvn+vxuBPQyYzY8YwChsvQzogwaeqW7pGH4Y2vwvsi7WToveiildzXIZAF
dL2hoylP82JBPWg7SzS/39jteWAMgGe252aUno1+nqShT7dijmv32qGiQTjpv5/H
ivubJBUcxJs3uYVkI6sFZkV5yUvtfB2jhJEd8mZ72sgiwIcarh9VM/UvHopZACn4
MyS/rqjuK6ZYyghfW+Mzik5Oq/TzWIlHAgxLtEt5S9VObezWn5j9LqSkCMg5Z5Pg
MRVtSW9A5BPfIAdiAzIrtHIxFwKzFI8PmInYY3Q6NuRicXMtb+2qt7RktdqoIsAK
6npRa3+5A8yRGVtwVpWNPLQXR3G08v5bdJC2vz2w6UrvDOhBjwUMfzDUqov09tfC
v+8iiOO5ivVTGGk4QhTI8sbYSqAVpL97o+4bFLUXg4N5pSegCpYQgBTqs4N5Xdv5
7nxDhclrOXriERtz7I1FEBFq+cEgeSUu0NdCeoG2lUz6tsxEcYzo0WheyWjREP5E
9lVYwL8FaQ==
=FbGF
-END PGP SIGNATURE End Message ---

Bug#962194: lintian-brush: autopkgtest failure on s390x

[Michael R. Crusoe]

On Fri, 5 Jun 2020 11:29:55 +0200 Gianfranco Costamagna <
locutusofb...@debian.org> wrote:
> Hello,
>
> (this is on zelenka)
>
> python3 test.py
> Traceback (most recent call last):
>   File "test.py", line 16, in 
> yaml.load(f)
>   File "/usr/lib/python3/dist-packages/ruamel/yaml/main.py", line 331, in
load
> return constructor.get_single_data()
>   File "/usr/lib/python3/dist-packages/ruamel/yaml/constructor.py", line
109, in get_single_data
> node = self.composer.get_single_node()
>   File "ext/_ruamel_yaml.pyx", line 701, in
_ruamel_yaml.CParser.get_single_node
>   File "ext/_ruamel_yaml.pyx", line 904, in
_ruamel_yaml.CParser._parse_next_event
> ruamel.yaml.reader.ReaderError: unacceptable character #x: control
characters are not allowed
>   in "", position 244
>
>
> So, yes, looks like yaml has an endianess issue?
>

I see the cparser is being used. Can you try the same using ruamel.yaml's
pure Python parser?

https://yaml.readthedocs.io/en/latest/basicuse.html#more-examples

from ruamel.yaml import YAML

yaml=YAML(typ="safe", pure=True)
yaml.load(f)

If that works, then we might be able to make a workaround to default to the
pure Python version on big endian systems. To be reverted once upstream has
a proper fix to the cpython code, of course.

Note: ruamel.yaml is mostly a one person (Anthon van der Neut) project, so
a fix might take a while. Fans of s390x and other big endian architectures
are very welcome to develop a patch!

https://yaml.readthedocs.io/en/latest/contributing.html

--
Michael R. Crusoe

Bug#971789: marked as done (FTBFS: Could not determine section for ./.gopath/src/github.com/docker/cli/man/man1/docker-attach.1)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2020 06:49:18 +
with message-id 
and subject line Bug#971789: fixed in docker.io 19.03.13+dfsg1-3
has caused the Debian Bug report #971789,
regarding FTBFS: Could not determine section for 
./.gopath/src/github.com/docker/cli/man/man1/docker-attach.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.)


-- 
971789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: docker.io
Version: 19.03.13+dfsg1-2
Severity: serious
X-Debbugs-Cc: z...@debian.org

Maybe due to the go-md2man v2 transition, docker.io is now FTBFS.

dh_installman: warning: Section for 
./.gopath/src/github.com/docker/cli/man/man1/docker-attach.1 is computed as 
"2020", which is not a valid section
dh_installman: error: Could not determine section for 
./.gopath/src/github.com/docker/cli/man/man1/docker-attach.1
dh_installman: error: Aborting due to earlier error
make: *** [debian/rules:40: binary] Error 25
--- End Message ---
--- Begin Message ---
Source: docker.io
Source-Version: 19.03.13+dfsg1-3
Done: Arnaud Rebillout 

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

Debian distribution maintenance software
pp.
Arnaud Rebillout  (supplier of updated docker.io 
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, 14 Oct 2020 11:38:00 +0700
Source: docker.io
Architecture: source
Version: 19.03.13+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Arnaud Rebillout 
Changed-By: Arnaud Rebillout 
Closes: 971789
Changes:
 docker.io (19.03.13+dfsg1-3) unstable; urgency=medium
 .
   * Add patch to fix spf13/cobra (tianon) (Closes: #971789)
Checksums-Sha1:
 a67060214144a5285f093ac2bf5de372e49f059a 8670 docker.io_19.03.13+dfsg1-3.dsc
 38bad7d79816d840157b76bbcfc4d7b6285d80bb 52400 
docker.io_19.03.13+dfsg1-3.debian.tar.xz
 c68a7d78c5ea9bc609539110eaaad6ffc189199b 7504 
docker.io_19.03.13+dfsg1-3_source.buildinfo
Checksums-Sha256:
 ac76b47290aa0b04b60c6179a68ebf47169459e553b381db883342b496601e3f 8670 
docker.io_19.03.13+dfsg1-3.dsc
 ab72e7835c52858de2d4be7d3e6b4439852209d02d29dd5e206eb43a640b8b00 52400 
docker.io_19.03.13+dfsg1-3.debian.tar.xz
 57dd5024156a892a80e0bfc5bae52b153fa14bd3948ef028b6ae8a74d6ad89ea 7504 
docker.io_19.03.13+dfsg1-3_source.buildinfo
Files:
 7441489f199d1fcc27a87ba52cbc46f6 8670 admin optional 
docker.io_19.03.13+dfsg1-3.dsc
 b7649e51884d4725b4c09f48677657dd 52400 admin optional 
docker.io_19.03.13+dfsg1-3.debian.tar.xz
 9068c453e509f1f7f8dfd58951ab6f95 7504 admin optional 
docker.io_19.03.13+dfsg1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJLBAEBCgA1FiEE0Kl7ndbut+9n4bYs5yXoeRRgAhYFAl+GmiMXHGVsYm91bGFu
Z2Vyb0BnbWFpbC5jb20ACgkQ5yXoeRRgAhZmvhAAlzIYC96QrWYgaPVETUfvXcdS
QENmI0IExWta+tkx2rsE/sWfyRZ04uyNUJemTAxiDMTurVPANmTq0U82xz1unV4c
XXJ2y0GjDYEAF9eNTnLSugzMy+khPErQ4X1IwM+Deeqf7mU6scDhbHGTacU3YOcL
SVWAJW/fwFxjTAxHHb13j0Uk/sa23LdVuHn0DisKhJk7TJH/whfD4ADTFW9275F6
dIw41bPou9xiXWkLKRYvhjU3LdW6yN8slBNAdB9NbORYFnQjnHD9RItkE6Lr6j4q
c+b65WpHhVKPsmH54yzTcqqKKjbYSOTHeV9FVS8NPbpiNtIFv/Q/NvbcTGa7YFpv
z4lz6k2LrNoCfKMrmvmD+K9KKoBfXrL5aiOqnEawYPwT3ySw41lnCpR0qYjLP3mW
1SpObPkygj1zGpQ/FYIDc/yORNPv0OWtFZcVvYLcLZPXj/pg7kkk9ICxr0Jv7LT1
3fyRKSQlWPzLg39xcFEjjLOpjWB7UYFTc0C6QSBP+vLrlU0f3/y3axwEcSCKB6zY
2VYU43WfqNAWdtd+MIx//3k4KfTJOED4K8G7BXcz/QR8CeZDLRKXh1KVSY71CzaI
kXa0UaZuahoKbssDULsm1/uULVEPg6gGgVTjcJbkvHiuZhBpekAoP+TxztYDBRTK
+XbG7ilteI+JLncekyY=
=ZQnR
-END PGP SIGNATURE End Message ---

Processed: raising severity of python 3.9 issues, now a supported python3 version

[Debian Bug Tracking System]

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

> severity 971916 serious
Bug #971916 [src:basemap] basemap ftbfs with python3-defaults (python3.9)
Bug #966969 [src:basemap] basemap: FTBFS: dh_install: error: missing files, 
aborting
Ignoring request to change severity of Bug 971916 to the same value.
Ignoring request to change severity of Bug 966969 to the same value.
> severity 971995 serious
Bug #971995 [src:python-greenlet] python-greenlet ftbfs with python3-defaults 
(python3.9) from experimental
Bug #972025 [src:python-greenlet] python-greenlet ftbfs with python3.9 as 
supported python version
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> severity 972016 serious
Bug #972016 [src:py-lmdb] py-lmdb ftbfs with python3.9
Severity set to 'serious' from 'important'
> severity 972022 serious
Bug #972022 [libxml2] python-dmicode ftbfs with python3.9 as supported python 
version
Severity set to 'serious' from 'important'
> severity 972026 serious
Bug #972026 [src:python-pyo] python-pyo ftbfs with python3.9 as supported 
python version
Severity set to 'serious' from 'important'
> severity 972027 serious
Bug #972027 [src:pycxx] pycxx needs a sourceful upload to support python3.9
Severity set to 'serious' from 'important'
> severity 971918 serious
Bug #971918 [src:pydantic] pydantic ftbfs with python3-defaults (python3.9) 
from experimental
Severity set to 'serious' from 'important'
> severity 972006 serious
Bug #972006 [src:compyle] pycompyle ftbfs with python3.9 (test failures)
Severity set to 'serious' from 'important'
> severity 972009 serious
Bug #972009 [src:gudhi] gudhi ftbfs with python3.9 as supported python version
Severity set to 'serious' from 'important'
> severity 972012 serious
Bug #972012 [src:mod-wsgi] mod-wsgi ftbfs with python3.9 as supported python 
version
Severity set to 'serious' from 'important'
> severity 972014 serious
Bug #972014 [src:onnx] onnx ftbfs with python3.9 as supported python version
Severity set to 'serious' from 'important'
> severity 972018 serious
Bug #972018 [src:pyfftw] pyfftw ftbfs with python3.9 as supported python version
Severity set to 'serious' from 'important'
> severity 972019 serious
Bug #972019 [src:pygame] pygame ftbfs with python3.9 as supported python version
Severity set to 'serious' from 'important'
> severity 972021 serious
Bug #972021 [src:pysph] pysph ftbfs with python3.9 as supported python version
Severity set to 'serious' from 'important'
> severity 972023 serious
Bug #972023 [src:python-enable] python-enable ftbfs with python3.9 as supported 
python3 version
Severity set to 'serious' from 'important'
> severity 972024 serious
Bug #972024 [src:python-geotiepoints] python-geotiepoints ftbfs with python3.9 
as supported python3 version
Severity set to 'serious' from 'important'
> severity 972028 serious
Bug #972028 [src:python-acora] python-acora ftbfs with python3.9 as supported 
python version
Severity set to 'serious' from 'important'
> severity 972032 serious
Bug #972032 [src:setools] python-setools ftbfs with python3.9 as supported 
python version
Severity set to 'serious' from 'important'
> severity 971910 serious
Bug #971910 [src:python-cffi] fix ftbfs with python3.9
Severity set to 'serious' from 'important'
> severity 971936 serious
Bug #971936 [src:blist] blist ftbfs with python3-defaults (python3.9) from 
experimental
Severity set to 'serious' from 'important'
> severity 972013 serious
Bug #972013 [src:mypy] mypy ftbfs with python3.9
Severity set to 'serious' from 'important'
> severity 972015 serious
Bug #972015 [src:pandas] pandas ftbfs with python3 as supported python version
Bug #972033 [src:pandas] pandas ftbfs with python3.9 as supported python version
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> severity 972029 serious
Bug #972029 [src:python-udatetime] python-udatetime ftbfs with python3.9 as 
supported python3 version
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
966969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966969
971910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971910
971916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971916
971918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971918
971936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971936
971995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971995
972006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972006
972009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972009
972012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972012
972013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972013
972014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972014
972015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972015
972016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972016
972018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972018
972019: 

Bug#971789: FTBFS: Could not determine section for ./.gopath/src/github.com/docker/cli/man/man1/docker-attach.1

[El boulangero]

I could solve the issue by patching spf13/cobra as suggested by Tianon. See
[1] for the patch. I just uploaded the package.

Since docker.io has to embed spf13/cobra, I could patch it there. But if
other packages in Debian have the same issue, then maybe this patch should
be applied to golang-github-spf13-cobra-dev.

Also, not that apparently the upstream bug is at
https://github.com/spf13/cobra/issues/1049



[1]:
https://salsa.debian.org/docker-team/docker/-/blob/master/debian/patches/cli-fix-spf13-cobra-man-docs.patch

On Tue, Oct 13, 2020 at 7:27 PM Sascha Steinbiss  wrote:

> Hi,
>
> has anyone taken any action here already? Some of my packages are
> affected by this as well.
>
> Cheers
> Sascha
>

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 945327 0.13.4-1
Bug #945327 {Done: "Michael R. Crusoe" } 
[src:python-pomegranate] python-pomegranate ftbfs in unstable
Marked as fixed in versions python-pomegranate/0.13.4-1.
> --
Stopping processing here.

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

Bug#972100: [Pkg-rust-maintainers] Bug#972100: CVE-2019-15547 CVE-2019-15548 (rust-ncurses)

[Alexander Kjäll]

Hi

I'm slowly working my way towards packaging ripasso, which doesn't use
ncurses-rs due to the above security problems. But it does use cursive
( https://crates.io/crates/cursive ) which have ncurses-rs as an
optional dependency.

Currently the rust packaging system in debian requires all optional
dependencies to be present in order to build the package.

I have suggested to the cursive maintainer to remove ncurses-rs due to
the above security concerns here (
https://github.com/gyscos/cursive/issues/488 ) but I suspect that this
would be considered quite a disruptive change, I have also started to
rewrite it to use ncursesw but haven't had the time/skill to finish
that work yet.

I'm not opposed to removing it, as that kind of unmaintained code with
known security problems are exploits waiting to happen. But it would
also require a lot of work to happen before we can package anything
that depends on cursive into debian.

best regards
Alexander Kjäll

Den ons 14 okt. 2020 kl 05:57 skrev peter green :
>
> I just looked at this issue.
>
> rust-ncurses is a thin wrapper around ncurses. It exposes unsafe (in the rust 
> sense) C
> APIs to safe rust code. The rust security team consider this to be a 
> vulnerability.
>
> There is more discussion of this issue at 
> https://github.com/jeaye/ncurses-rs/issues/188
> the fix would be to mark most if not all of the functions exposed by the 
> library as
> unsafe and release a new major version of the library. Any reverse 
> dependencies would
> then need to be adapted to work with the new unsafe functions. The upstream 
> maintainer
> has indicated they would be accepting of a pull request but is not interested 
> in doing
> the work themselves.
>
> There is also another wrapper called ncursesw which seems to be better 
> maintained
> and offers both low-level wrappers (correctly marked as unsafe) and 
> higher-level
> wrappers (some of which are safe). It is not packaged in Debian.
>
> I looked to see what if-any packages in Debian use rust-ncurses and I did not 
> find
> any in either buster, bullseye or sid. Is there a reason to keep this package 
> around?
>
> ___
> Pkg-rust-maintainers mailing list
> pkg-rust-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers

Bug#971789: marked as pending in docker.io

[Arnaud Rebillout]

Control: tag -1 pending

Hello,

Bug #971789 in docker.io 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/docker-team/docker/-/commit/5166c4c6e75ff4c1d1b8b8ebaa9ae367cc1ee272


Add patch to fix spf13/cobra (tianon) (Closes: #971789)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/971789

Processed: Bug#971789 marked as pending in docker.io

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #971789 [docker.io] FTBFS: Could not determine section for 
./.gopath/src/github.com/docker/cli/man/man1/docker-attach.1
Added tag(s) pending.

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