Bug#931519: Wajig update to resolve bug - wajig version 3.2.20

[Graham Williams]

Latest version of wajig (3.2.20) on https://github.com/gjwgit/wajig has
resolved the issue. Currently working on an update to Debian repo.

Regards,
Graham

Processed: fixed 971178 in 20.44.18297-1

[Debian Bug Tracking System]

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

> fixed 971178 20.44.18297-1
Bug #971178 [src:intel-compute-runtime] intel-compute-runtime: FTBFS: make[3]: 
*** 
[igdrcl_lib_release/scheduler/CMakeFiles/scheduler_Gen9core.dir/build.make:84: 
bin/scheduler/x64/gen9/scheduler_Gen9core.bin] Error 245
Marked as fixed in versions intel-compute-runtime/20.44.18297-1.
> thanks
Stopping processing here.

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

Bug#974564: marked as done (mpi4py: autopkgtest regression on amd64, arm64 and ppc64el: Segmentation fault)

[Debian Bug Tracking System]

Your message dated Sat, 14 Nov 2020 05:33:19 +
with message-id 
and subject line Bug#974560: fixed in mpi4py 3.0.3-7
has caused the Debian Bug report #974560,
regarding mpi4py: autopkgtest regression on amd64, arm64 and ppc64el: 
Segmentation fault
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.)


-- 
974560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpi4py
Version: 3.0.3-6
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent change in testing the autopkgtest of mpi4py started to
fail in testing when that autopkgtest is run on amd64, arm64 and
ppc64el. On top of that, the pure testing runs on ppc64el currently time
out.

Can you please investigate the situation and fix it?

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mpi4py/7973800/log.gz

FAILED  [
82%]test/test_rma.py::TestRMAWorld::testAccumulate FAILED
   [ 82%]
test/test_rma.py::TestRMASelf::testStartCompletePostTest
test/test_rma.py::TestRMASelf::testStartCompletePostTest PASSED
 [ 82%]
test/test_rma.py::TestRMASelf::testStartCompletePostWait PASSED
 [ 82%]
test/test_rma.py::TestRMASelf::testStartCompletePostWait PASSEDPASSED
   [ 82%]  [ 82%]
test/test_rma.py::TestRMASelf::testSync
test/test_rma.py::TestRMASelf::testSync PASSED
 [ 83%]PASSED   [ 83%]
test/test_rma.py::TestRMAWorld::testAccumulate
test/test_rma.py::TestRMAWorld::testAccumulate
--
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--
--
mpiexec noticed that process rank 1 with PID 0 on node ci-310-4b44f698
exited on signal 11 (Segmentation fault).
--





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mpi4py
Source-Version: 3.0.3-7
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated mpi4py 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: Sat, 14 Nov 2020 12:56:39 +0800
Source: mpi4py
Architecture: source
Version: 3.0.3-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 974560
Changes:
 mpi4py (3.0.3-7) unstable; urgency=medium
 .
   * Team upload.
   * extend debian patch skip_failing_test_rma.patch to skip the
 affected tests for any openmpi release >=4.0.4,<4.1. Review fails
 when openmpi 4.1 is released. Closes: #974560.
Checksums-Sha1:
 8e9d12d745f24cd35dbe093974390a5ee5e5e968 2444 mpi4py_3.0.3-7.dsc
 2916543ee255142b97611e8a7c143b0aa0048710 10704 mpi4py_3.0.3-7.debian.tar.xz
Checksums-Sha256:
 b126019616d800c1eac807e84628acca58de594a5939704d0bc7c1dc9bb1663b 2444 
mpi4py_3.0.3-7.dsc
 a4fdaad361223048553e3a61e61ef088de91303fefa8c23ebac516ac72b2fd86 10704 
mpi4py_3.0.3-7.debian.tar.xz
Files:
 989470dd2e157df6a46d0e900afbec3f 2444 python optional mpi4py_3.0.3-7.dsc
 195186790e0d3bad2837d5c90d2a0ff7 10704 python optional 
mpi4py_3.0.3-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl+vZ98ACgkQVz7x5L1a
AfqBkRAAmSMV1swD81FBaO+GZa5uUSxLkygUXzd+c2rbpK6Ohm7/a7lqUr//LT8e
MrzguovxdHRnMGIcPR9oxMLf7z716FlJJyF39Z1g/VGotPnua67o9eIm0kA78jkA
q9tPxhfsgp+Py9jRvzVvjdap1+Y7iCnByfrcofFEF9nyhY63kG/vYkh1zTSI07Uk
BmsQkcU7g3kjDbavzXqEE4mYmN82x7dKdSPGHUppQvjMAColgtNVT38SOCM0+nyD
iuUzlE0Gs0DvbxsEm/aqLPdAqS1CBirwmZ1b5oIZO5jXm1jbKHOyCLF4sO9OrZ1A
O6ZyW+ZDzZNWjnr0joXi1SHg7rT5ILgMsFp9goO8cKKE0GrgzfNVA5eYgc1KButM
Y9ANLu5HZPK2iu7PTOM7VTIkN4Rix/AFOa9MN3FnOr/heotUlKy

Bug#974560: marked as done (mpi4py: autopkgtest regression on amd64, arm64 and ppc64el: Segmentation fault)

[Debian Bug Tracking System]

Your message dated Sat, 14 Nov 2020 05:33:19 +
with message-id 
and subject line Bug#974560: fixed in mpi4py 3.0.3-7
has caused the Debian Bug report #974560,
regarding mpi4py: autopkgtest regression on amd64, arm64 and ppc64el: 
Segmentation fault
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.)


-- 
974560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpi4py
Version: 3.0.3-6
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent change in testing the autopkgtest of mpi4py started to
fail in testing when that autopkgtest is run on amd64, arm64 and
ppc64el. On top of that, the pure testing runs on ppc64el currently time
out.

Can you please investigate the situation and fix it?

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mpi4py/7973800/log.gz

FAILED  [
82%]test/test_rma.py::TestRMAWorld::testAccumulate FAILED
   [ 82%]
test/test_rma.py::TestRMASelf::testStartCompletePostTest
test/test_rma.py::TestRMASelf::testStartCompletePostTest PASSED
 [ 82%]
test/test_rma.py::TestRMASelf::testStartCompletePostWait PASSED
 [ 82%]
test/test_rma.py::TestRMASelf::testStartCompletePostWait PASSEDPASSED
   [ 82%]  [ 82%]
test/test_rma.py::TestRMASelf::testSync
test/test_rma.py::TestRMASelf::testSync PASSED
 [ 83%]PASSED   [ 83%]
test/test_rma.py::TestRMAWorld::testAccumulate
test/test_rma.py::TestRMAWorld::testAccumulate
--
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--
--
mpiexec noticed that process rank 1 with PID 0 on node ci-310-4b44f698
exited on signal 11 (Segmentation fault).
--



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mpi4py
Source-Version: 3.0.3-7
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated mpi4py 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: Sat, 14 Nov 2020 12:56:39 +0800
Source: mpi4py
Architecture: source
Version: 3.0.3-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 974560
Changes:
 mpi4py (3.0.3-7) unstable; urgency=medium
 .
   * Team upload.
   * extend debian patch skip_failing_test_rma.patch to skip the
 affected tests for any openmpi release >=4.0.4,<4.1. Review fails
 when openmpi 4.1 is released. Closes: #974560.
Checksums-Sha1:
 8e9d12d745f24cd35dbe093974390a5ee5e5e968 2444 mpi4py_3.0.3-7.dsc
 2916543ee255142b97611e8a7c143b0aa0048710 10704 mpi4py_3.0.3-7.debian.tar.xz
Checksums-Sha256:
 b126019616d800c1eac807e84628acca58de594a5939704d0bc7c1dc9bb1663b 2444 
mpi4py_3.0.3-7.dsc
 a4fdaad361223048553e3a61e61ef088de91303fefa8c23ebac516ac72b2fd86 10704 
mpi4py_3.0.3-7.debian.tar.xz
Files:
 989470dd2e157df6a46d0e900afbec3f 2444 python optional mpi4py_3.0.3-7.dsc
 195186790e0d3bad2837d5c90d2a0ff7 10704 python optional 
mpi4py_3.0.3-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl+vZ98ACgkQVz7x5L1a
AfqBkRAAmSMV1swD81FBaO+GZa5uUSxLkygUXzd+c2rbpK6Ohm7/a7lqUr//LT8e
MrzguovxdHRnMGIcPR9oxMLf7z716FlJJyF39Z1g/VGotPnua67o9eIm0kA78jkA
q9tPxhfsgp+Py9jRvzVvjdap1+Y7iCnByfrcofFEF9nyhY63kG/vYkh1zTSI07Uk
BmsQkcU7g3kjDbavzXqEE4mYmN82x7dKdSPGHUppQvjMAColgtNVT38SOCM0+nyD
iuUzlE0Gs0DvbxsEm/aqLPdAqS1CBirwmZ1b5oIZO5jXm1jbKHOyCLF4sO9OrZ1A
O6ZyW+ZDzZNWjnr0joXi1SHg7rT5ILgMsFp9goO8cKKE0GrgzfNVA5eYgc1KButM
Y9ANLu5HZPK2iu7PTOM7VTIkN4Rix/AFOa9MN3FnOr/heotUlKyDE

Bug#974560: marked as pending in mpi4py

[Drew Parsons]

Control: tag -1 pending

Hello,

Bug #974560 in mpi4py 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/science-team/mpi4py/-/commit/1ee01a245b7097a46da95489a5e962c3165ebfa2


extend debian patch skip_failing_test_rma.patch to openmpi <4.1

skip the affected tests for any openmpi release >=4.0.4,<4.1.

Review failures again when openmpi 4.1 is released.

Closes: #974560.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/974560

Processed: Bug#974560 marked as pending in mpi4py

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #974560 [src:mpi4py] mpi4py: autopkgtest regression on amd64, arm64 and 
ppc64el: Segmentation fault
Bug #974564 [src:mpi4py] mpi4py: autopkgtest regression on amd64, arm64 and 
ppc64el: Segmentation fault
Added tag(s) pending.
Added tag(s) pending.

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

Processed: Reassign bugs after the split of mime-support

[Debian Bug Tracking System]

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

> reassign 930908 mailcap
Bug #930908 [mime-support] general: incorrect rules for %s in /etc/mailcap 
yielding potentially unquoted metacharacters
Bug reassigned from package 'mime-support' to 'mailcap'.
Ignoring request to alter found versions of bug #930908 to the same values 
previously set
Ignoring request to alter fixed versions of bug #930908 to the same values 
previously set
> reassign 935426 mailcap
Bug #935426 [mime-support] mailcap.order entries aren't always keyed by package 
name
Bug reassigned from package 'mime-support' to 'mailcap'.
No longer marked as found in versions mime-support/3.62.
Ignoring request to alter fixed versions of bug #935426 to the same values 
previously set
> reassign 964723 mailcap
Bug #964723 [mime-support] Ordering of entries: the calibre opens everything 
problem
Bug reassigned from package 'mime-support' to 'mailcap'.
No longer marked as found in versions mime-support/3.62.
Ignoring request to alter fixed versions of bug #964723 to the same values 
previously set
> reassign 949992 mailcap
Bug #949992 [mime-support] Does not take subprocess down when killed
Bug reassigned from package 'mime-support' to 'mailcap'.
No longer marked as found in versions mime-support/3.64.
Ignoring request to alter fixed versions of bug #949992 to the same values 
previously set
> reassign 573518 media-types
Bug #573518 [mime-support] mime-support: upstream and out of date mime.types
Bug reassigned from package 'mime-support' to 'media-types'.
No longer marked as found in versions mime-support/3.48-1.
Ignoring request to alter fixed versions of bug #573518 to the same values 
previously set
> reassign 823480 mailcap
Bug #823480 [mime-support] Error: no "view" mailcap rules found for type 
"inode/directory"
Bug reassigned from package 'mime-support' to 'mailcap'.
No longer marked as found in versions mime-support/3.60.
Ignoring request to alter fixed versions of bug #823480 to the same values 
previously set
> reassign 866290 mailcap
Bug #866290 [mime-support] mime-support: maintainer script(s) not using strict 
mode
Bug reassigned from package 'mime-support' to 'mailcap'.
No longer marked as found in versions mime-support/3.60.
Ignoring request to alter fixed versions of bug #866290 to the same values 
previously set
> reassign 908183 media-types
Bug #908183 [mime-support] mime-support: There are 2 entries for sh extension
Bug reassigned from package 'mime-support' to 'media-types'.
No longer marked as found in versions mime-support/3.60.
Ignoring request to alter fixed versions of bug #908183 to the same values 
previously set
> reassign 928037 mailcap
Bug #928037 [mime-support] mailcap(5): please document security considerations 
about %-escapes
Bug reassigned from package 'mime-support' to 'mailcap'.
No longer marked as found in versions mime-support/3.60.
Ignoring request to alter fixed versions of bug #928037 to the same values 
previously set
> reassign 949795 media-types
Bug #949795 [mime-support] mime-support: x-pascal mime type misses an extension
Bug reassigned from package 'mime-support' to 'media-types'.
No longer marked as found in versions 3.60ubuntu1.
Ignoring request to alter fixed versions of bug #949795 to the same values 
previously set
> reassign 971011 media-types
Bug #971011 [mime-support] missing "webp" extension
Bug reassigned from package 'mime-support' to 'media-types'.
No longer marked as found in versions mime-support/3.64.
Ignoring request to alter fixed versions of bug #971011 to the same values 
previously set
> reassign 935053 mailcap
Bug #935053 [mime-support] run-mimecap.1: Fix lines with a misused two-font 
marco
Bug reassigned from package 'mime-support' to 'mailcap'.
No longer marked as found in versions mime-support/3.63.
Ignoring request to alter fixed versions of bug #935053 to the same values 
previously set
> reassign 935059 mailcap
Bug #935059 [mime-support] update-mime.8: Fix lines with a misused two-fonts 
macro
Bug reassigned from package 'mime-support' to 'mailcap'.
No longer marked as found in versions mime-support/3.63.
Ignoring request to alter fixed versions of bug #935059 to the same values 
previously set
> reassign 803996 mailcap
Bug #803996 [mime-support] update-mime unnecessarily updates /etc/mailcap
Bug reassigned from package 'mime-support' to 'mailcap'.
No longer marked as found in versions mime-support/3.59.
Ignoring request to alter fixed versions of bug #803996 to the same values 
previously set
> reassign 935377 mailcap
Bug #935377 [mime-support] run-mailcap: "my" variable $file masks earlier 
declaration in same scope
Bug reassigned from package 'mime-support' to 'mailcap'.
No longer marked as found in versions mime-support/3.63.
Ignoring request to alter fixed versions of bug #935377 to the same values 
previously set
> reassign 291015 mailcap
Bug #291015 [mime-support] mime-support: run‐mailcap to understand URL notation 
and start sensible-browser if required.
Bug reassig

Bug#974563: corosync unable to communicate with pacemaker 1.1.16-1+deb9u1 which contains the fix for CVE-2020-25654

[Markus Koschany]

Am Freitag, den 13.11.2020, 23:13 -0300 schrieb Alejandro Taboada:
> Hello Markus,
> 
> It doesn’t work. The output log is quite different. I throws a timeout and
> just at the end the “unprivileged client crmd”.
> See attached log.

I'm sorry but I uploaded an older version that missed a do_reply line. That's
why are you seeing timeouts now. Now I have uploaded the correct version from
my test server to https://people.debian.org/~apo/lts/pacemaker/

Please try again.

Regards,

Markus



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

Bug#974705: New dash package breaks systemds timedated test (hangs in wait)

[Michael Biebl]

Package: dash
Version: 0.5.11+git20200708+dd9ef66-2
Severity: serious

Hi,

the latest update of dash seems to have broken the systemd autopkgtest
suite, specifically
https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/debian/tests/timedated

Afaics, the sh script get's stuck at the "wait" call at
https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/debian/tests/timedated#L166

Downgrading dash to 0.5.10.2-7 makes the test pass again.

Thus filing with RC to hopefully prevent testing migration until the
root cause is found.

Regards,
Michael



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

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

Versions of packages dash depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  debianutils4.11.2
ii  dpkg   1.20.5
ii  libc6  2.31-4

dash recommends no packages.

dash suggests no packages.

-- debconf information excluded

Processed: severity of 974686 is serious

[Debian Bug Tracking System]

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

> severity 974686 serious
Bug #974686 [python3-blockdev] python3-blockdev: Missing dependencies, without 
deps to gir1.2-blockdev-2.0 the python module in unsable
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

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

Processed: pcp: FTBFS on some archs: Cannot find (any matches for) "usr/lib/pcp/pmdas/infiniband[...]

[Debian Bug Tracking System]

Processing control commands:

> block 968912 with -1
Bug #968912 [release.debian.org] transition: perl 5.32
968912 was blocked by: 968913 972274 974061 961157 974021 964902 961208 974134 
974058 974055 972275 974143 961154 961152 973010 974063 974574 960863 961155 
974170
968912 was not blocking any bugs.
Added blocking bug(s) of 968912: 974704

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

Bug#974704: pcp: FTBFS on some archs: Cannot find (any matches for) "usr/lib/pcp/pmdas/infiniband[...]

[Dominic Hargreaves]

Source: pcp
Version: 5.2.2-1
Severity: serious
Justification: FTBFS on archs that previously worked
User: debian-p...@lists.debian.org
Usertags: perl-5.32-transition
Control: block 968912 with -1

This package FTBFS on the architectures which don't have bpftrace as a
dependency since:

dh_install: warning: Cannot find (any matches for) 
"usr/lib/pcp/pmdas/infiniband/Install" (tried in debian/pcp, debian/tmp)

dh_install: warning: pcp-pmda-infiniband missing files: 
usr/lib/pcp/pmdas/infiniband/Install
...
dh_install: error: missing files, aborting

See 
https://buildd.debian.org/status/fetch.php?pkg=pcp&arch=armel&ver=5.2.2-1&stamp=1605310204&raw=0
and https://buildd.debian.org/status/package.php?p=pcp

for full details.

Thanks
Dominic

Bug#974702: intel-opencl-icd causes all OpenCL programs to abort

[Giuseppe Bilotta]

Package: intel-opencl-icd
Followup-For: Bug #974702

Some additional information: I have tried downgrading to previous
versions of the package, and I found out that:

intel-opencl-icd 20.13.16352-1 has the issue
intel-opencl-icd 20.02.15268-1 has not

In fact, with 20.02 clinfo at least works, even though kernels fail to
compile for this ICD giving a CL_OUT_OF_HOST_MEMORY (-6) error.

If I downgrate libigc1 and libigdfcl1 to 1.0.3627-2, both 20.02 and
20.13 work correctly, but 20.37.17906-1 still aborts.


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

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

Versions of packages intel-opencl-icd depends on:
ii  libc62.31-4
ii  libgcc-s1 [libgcc1]  10.2.0-17
ii  libigc1  1.0.5353.1-2
ii  libigdfcl1   1.0.5353.1-2
ii  libigdgmm11  20.3.2+ds1-1
ii  libstdc++6   10.2.0-17
ii  ocl-icd-libopencl1   2.2.12-4

intel-opencl-icd recommends no packages.

intel-opencl-icd suggests no packages.

-- no debconf information

Bug#974702: intel-opencl-icd causes all OpenCL programs to abort

[Giuseppe Bilotta]

Package: intel-opencl-icd
Version: 20.37.17906-1
Severity: critical

When this package is installed, any OpenCL program will abort with the
message

Abort was called at 42 line in file:
/build/intel-compute-runtime-WsWnhf/intel-compute-runtime-20.37.17906/shared/source/built_ins/built_ins.cpp
Application Error

This is reproducible with a simple `clinfo -l`, but even something like
LibreOffice with OpenCL support enabled will fail to start (making it
impossible to actually even the LibreOffice configuration to disable
OpenCL), which is the reason for the critical severity.

Running `clinfo -l` under gdb shows the following backtrace:

#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x77da6537 in __GI_abort () at abort.c:79
#2  0x76baab53 in NEO::abortExecution () at 
./shared/source/helpers/abort.cpp:14
#3  0x76bc0b71 in NEO::abortUnrecoverable (line=line@entry=42, 
file=file@entry=0x76f1b868 
"/build/intel-compute-runtime-WsWnhf/intel-compute-runtime-20.37.17906/shared/source/built_ins/built_ins.cpp")
at ./shared/source/helpers/debug_helpers.cpp:24
#4  0x76ed07b4 in operator() (__closure=0x7fffdd60) at 
./shared/source/built_ins/built_ins.cpp:42
#5  std::__invoke_impl&> (__f=...) at /usr/include/c++/10/bits/invoke.h:60
#6  std::__invoke&> (__fn=...) at /usr/include/c++/10/bits/invoke.h:95
#7  operator() (this=) at /usr/include/c++/10/mutex:717
#8  operator() (this=0x0) at /usr/include/c++/10/mutex:722
#9  _FUN () at /usr/include/c++/10/mutex:722
#10 0x7710b34f in __pthread_once_slow (once_control=0x55786400, 
init_routine=0x77495fc0 <__once_proxy>) at pthread_once.c:116
#11 0x76ed0ae2 in __gthread_once (__func=, 
__once=0x55786400) at 
/usr/include/x86_64-linux-gnu/c++/10/bits/gthr-default.h:700
#12 std::call_once&> (__f=..., __once=...) at 
/usr/include/c++/10/mutex:729
#13 NEO::BuiltIns::getSipKernel (this=0x55785ff0, type=, 
device=...) at ./shared/source/built_ins/built_ins.cpp:64
#14 0x76be2516 in NEO::initSipKernel (type=, device=...) 
at ./opencl/source/helpers/built_ins_helper.cpp:16
#15 0x76c29878 in NEO::Platform::initialize (this=0x557841b0, 
devices=std::vector of length 1, capacity 1 = {...}) at 
./opencl/source/platform/platform.cpp:145
#16 0x76bdc85d in clGetPlatformIDs (numEntries=, 
platforms=, numPlatforms=) at 
./opencl/source/api/api.cpp:100
#17 0x76bdce54 in clIcdGetPlatformIDsKHR (numEntries=0, platforms=0x0, 
numPlatforms=0x7fffe04c) at ./opencl/source/api/api.cpp:136
#18 0x77f51ae3 in _find_and_check_platforms (num_icds=5) at 
ocl_icd_loader.c:445
#19 __initClIcd () at ocl_icd_loader.c:652
#20 _initClIcd_real () at ocl_icd_loader.c:702
#21 0x77f524e3 in _initClIcd () at ocl_icd_loader.c:724
#22 clGetPlatformIDs (num_entries=0, platforms=0x0, 
num_platforms=0x7fffe170) at ocl_icd_loader.c:846
#23 0x55564d42 in main (argc=2, argv=0x7fffe2d8) at 
src/clinfo.c:3351

Note that no OpenCL ICD should _ever_ invoke abort: OpenCL has specific
ways to pass failure information up to the caller, those shold be used
instead.

(That aside, it's unclear why the failure even happens in the first
place.)


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

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

Versions of packages intel-opencl-icd depends on:
ii  libc6   2.31-4
ii  libgcc-s1   10.2.0-17
ii  libigc1 1.0.5353.1-2
ii  libigdfcl1  1.0.5353.1-2
ii  libigdgmm11 20.3.2+ds1-1
ii  libstdc++6  10.2.0-17
ii  ocl-icd-libopencl1  2.2.12-4

intel-opencl-icd recommends no packages.

intel-opencl-icd suggests no packages.

-- no debconf information

Processed: bug 970878 is forwarded to https://bugs.ghostscript.com/show_bug.cgi?id=703143

[Debian Bug Tracking System]

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

> forwarded 970878 https://bugs.ghostscript.com/show_bug.cgi?id=703143
Bug #970878 [src:ghostscript] ghostscript breaks doc-rfc autopkgtest: 
segmentation fault
Set Bug forwarded-to-address to 
'https://bugs.ghostscript.com/show_bug.cgi?id=703143'.
> thanks
Stopping processing here.

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

Bug#974563: 9u1.3 works for me

[Philip Ward]

Thank you for the 9u1.3 packages. Just installed on one of my QA
clusters and it's working.

Phil Ward.

The University achieved an overall 5 stars in the QS World University Rankings 
2020
UK Sports University of the Year 2020 (Times Higher Good University Guide)
The University of Stirling is a charity registered in Scotland, number SC 
011159.

Bug#973010: marked as done (pcp is uninstallable on many architectures due to new bpftrace dependency)

[Debian Bug Tracking System]

Your message dated Fri, 13 Nov 2020 22:00:14 +
with message-id 
and subject line Bug#973010: fixed in pcp 5.2.2-1
has caused the Debian Bug report #973010,
regarding pcp is uninstallable on many architectures due to new bpftrace 
dependency
to be marked as done.

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

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


-- 
973010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pcp
Version: 5.2.1-1
Severity: serious
Tags: patch

The recent 5.2.1-1 upload made a dependency change to pcp:

 Package: pcp 
-Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, libpcp-pmda-perl, 
python3-pcp, python3, libpcp-web1
+Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, libpcp-pmda-perl, 
python3-pcp, python3, bpftrace (>= 0.9.2), libpcp-web1

But the "bpftrace" package only exists on a few architectures [1]. This is what
makes the package uninstallable and prevents testing migration [2].

Please fix
that at least by restricting the architectures, like so:

  Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, libpcp-pmda-perl, 
python3-pcp, python3, bpftrace (>= 0.9.2) [amd64 arm64 ppc64 ppc64el], 
libpcp-web1

Preferably you would also drop it to Recommends:, as hopefully bpftrace isn't
an absolute requirement for running PCP? I.e.

  Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, libpcp-pmda-perl, 
python3-pcp, python3, libpcp-web1
  Recommends: bpftrace (>= 0.9.2)

Thanks!

Martin

[1] https://packages.debian.org/sid/bpftrace
[2] https://tracker.debian.org/pkg/pcp


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: pcp
Source-Version: 5.2.2-1
Done: Nathan Scott 

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

Debian distribution maintenance software
pp.
Nathan Scott  (supplier of updated pcp 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, 11 Nov 2020 07:31:00 +1000
Source: pcp
Binary: libpcp-gui2 libpcp-gui2-dev libpcp-import-perl libpcp-import1 
libpcp-import1-dev libpcp-logsummary-perl libpcp-mmv-perl libpcp-mmv1 
libpcp-mmv1-dev libpcp-pmda-perl libpcp-pmda3 libpcp-pmda3-dev libpcp-trace2 
libpcp-trace2-dev libpcp-web1 libpcp-web1-dev libpcp3 libpcp3-dev pcp pcp-conf 
pcp-doc pcp-export-pcp2graphite pcp-export-pcp2influxdb pcp-export-zabbix-agent 
pcp-gui pcp-import-collectl2pcp pcp-import-ganglia2pcp pcp-import-iostat2pcp 
pcp-import-mrtg2pcp pcp-import-sar2pcp pcp-import-sheet2pcp pcp-pmda-infiniband 
pcp-testsuite python3-pcp
Architecture: source amd64 all
Version: 5.2.2-1
Distribution: unstable
Urgency: low
Maintainer: PCP Development Team 
Changed-By: Nathan Scott 
Description:
 libpcp-gui2 - Performance Co-Pilot graphical client tools library
 libpcp-gui2-dev - Performance Co-Pilot graphical client tools library and 
headers
 libpcp-import-perl - Performance Co-Pilot log import Perl module
 libpcp-import1 - Performance Co-Pilot data import library
 libpcp-import1-dev - Performance Co-Pilot data import library and headers
 libpcp-logsummary-perl - Performance Co-Pilot historical log summary module
 libpcp-mmv-perl - Performance Co-Pilot Memory Mapped Value Perl module
 libpcp-mmv1 - Performance Co-Pilot Memory Mapped Value client library
 libpcp-mmv1-dev - Performance Co-Pilot Memory Mapped Value library and headers
 libpcp-pmda-perl - Performance Co-Pilot Domain Agent Perl module
 libpcp-pmda3 - Performance Co-Pilot Domain Agent library
 libpcp-pmda3-dev - Performance Co-Pilot Domain Agent library and headers
 libpcp-trace2 - Performance Co-Pilot application tracing library
 libpcp-trace2-dev - Performance Co-Pilot application tracing library and 
headers
 libpcp-web1 - Performance Co-Pilot data import library
 libpcp-web1-dev - Performance Co-Pilot web tooling
 libpcp3- Performance Co-Pilot library
 libpcp3-dev - Performance Co-Pilot library and headers
 pcp- System level performance monitoring and performance management
 pcp-conf   - Performance Co-Pilot runtime configuration
 pcp-

Bug#973160: marked as done (pbbam: FTBFS: optional.hpp:1591:3: error: static assertion failed: If you want to output boost::optional, include header )

[Debian Bug Tracking System]

Your message dated Fri, 13 Nov 2020 22:00:12 +
with message-id 
and subject line Bug#973160: fixed in pbbam 1.6.0+dfsg-1
has caused the Debian Bug report #973160,
regarding pbbam: FTBFS: optional.hpp:1591:3: error: static assertion failed: If 
you want to output boost::optional, include header 

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


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

Hi,

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

Relevant part (hopefully):
> c++ -Itests/pbbam_test.p -Itests -I../tests -Iinclude -I../include 
> -I/usr/include -fdiagnostics-color=always -DNDEBUG -pipe 
> -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DBOOST_ALL_NO_LIB 
> -DGTEST_HAS_PTHREAD=1 -Wduplicated-cond -Wduplicated-branches -Wlogical-op 
> -Wrestrict -Wnull-dereference -Wuseless-cast -Wdouble-promotion -Wshadow 
> -Wformat=1 -MD -MQ tests/pbbam_test.p/src_test_ReadGroupInfo.cpp.o -MF 
> tests/pbbam_test.p/src_test_ReadGroupInfo.cpp.o.d -o 
> tests/pbbam_test.p/src_test_ReadGroupInfo.cpp.o -c 
> ../tests/src/test_ReadGroupInfo.cpp
> In file included from /usr/include/boost/optional/optional.hpp:33,
>  from /usr/include/boost/optional.hpp:15,
>  from ../include/pbbam/ReadGroupInfo.h:19,
>  from ../tests/src/test_ReadGroupInfo.cpp:13:
> /usr/include/boost/optional/optional.hpp: In instantiation of 
> ‘std::basic_ostream<_CharT, _Traits>& 
> boost::operator<<(std::basic_ostream<_CharT, _Traits>&, const 
> boost::optional_detail::optional_tag&) [with CharType = char; CharTrait = 
> std::char_traits]’:
> /usr/include/gtest/gtest-printers.h:217:9:   required from ‘static void 
> testing::internal::internal_stream_operator_without_lexical_name_lookup::StreamPrinter::PrintValue(const
>  T&, std::ostream*) [with T = boost::optional short unsigned int> >;  = void; 
>  = std::basic_ostream&; std::ostream = 
> std::basic_ostream]’
> /usr/include/gtest/gtest-printers.h:305:22:   required from ‘void 
> testing::internal::PrintWithFallback(const T&, std::ostream*) [with T = 
> boost::optional >; 
> std::ostream = std::basic_ostream]’
> /usr/include/gtest/gtest-printers.h:434:30:   required from ‘void 
> testing::internal::PrintTo(const T&, std::ostream*) [with T = 
> boost::optional >; 
> std::ostream = std::basic_ostream]’
> /usr/include/gtest/gtest-printers.h:630:12:   required from ‘static void 
> testing::internal::UniversalPrinter::Print(const T&, std::ostream*) [with 
> T = boost::optional >; 
> std::ostream = std::basic_ostream]’
> /usr/include/gtest/gtest-printers.h:858:30:   required from ‘void 
> testing::internal::UniversalPrint(const T&, std::ostream*) [with T = 
> boost::optional >; 
> std::ostream = std::basic_ostream]’
> /usr/include/gtest/gtest-printers.h:786:19:   [ skipping 2 instantiation 
> contexts, use -ftemplate-backtrace-limit=0 to disable ]
> /usr/include/gtest/gtest-printers.h:327:36:   required from ‘static 
> std::string testing::internal::FormatForComparison OtherOperand>::Format(const ToPrint&) [with ToPrint = 
> boost::optional >; 
> OtherOperand = boost::none_t; std::string = std::__cxx11::basic_string]’
> /usr/include/gtest/gtest-printers.h:408:45:   required from ‘std::string 
> testing::internal::FormatForComparisonFailureMessage(const T1&, const T2&) 
> [with T1 = boost::optional 
> >; T2 = boost::none_t; std::string = std::__cxx11::basic_string]’
> /usr/include/gtest/gtest.h:1528:53:   required from ‘testing::AssertionResult 
> testing::internal::CmpHelperEQFailure(const char*, const char*, const T1&, 
> const T2&) [with T1 = boost::none_t; T2 = boost::optional unsigned int, short unsigned int> >]’
> /usr/include/gtest/gtest.h:1549:28:   required from ‘testing::AssertionResult 
> testing::internal::CmpHelperEQ(const char*, const char*, const T1&, const 
> T2&) [with T1 = boost::none_t; T2 = boost::optional int, short unsigned int> >]’
> /usr/include/gtest/gtest.h:1572:23:   required from ‘static 
> testing::AssertionResult testing::internal::EqHelper::Compare(const char*, 
> const char*, const T1&, const T2&) [with T1 = boost::none_t; T2 = 
> boost::optional >; typename 
> std::enable_if<((! std::is_integral<_Tp>::value) || (! 
> std::is_pointer<_Dp>::valu

Bug#974096: marked as done (golang-github-c-bata-go-prompt: autopkgtest regression: cannot use &t.origTermios (type *unix.Termios) as type *syscall.Termios in argument to termios.Tcgetattr)

[Debian Bug Tracking System]

Your message dated Fri, 13 Nov 2020 14:15:25 -0700
with message-id <20201113211525.ga1526...@debian-e431.fok>
and subject line Bug#974096: fixed in golang-github-c-bata-go-prompt 0.2.5-1
has caused the Debian Bug report #974096,
regarding golang-github-c-bata-go-prompt: autopkgtest regression: cannot use 
&t.origTermios (type *unix.Termios) as type *syscall.Termios in argument to 
termios.Tcgetattr
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.)


-- 
974096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-c-bata-go-prompt
Version: 0.2.3+git20181109.b6d2b43-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of golang-github-c-bata-go-prompt the autopkgtest
of golang-github-c-bata-go-prompt fails in testing when that autopkgtest
is run with the binary packages of golang-github-c-bata-go-prompt from
unstable. It passes when run with only packages from testing. In tabular
form:

 passfail
golang-github-c-bata-go-prompt   from testing
   0.2.3+git20181109.b6d2b43-2
all others   from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=golang-github-c-bata-go-prompt

https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-c-bata-go-prompt/8063701/log.gz

autopkgtest [17:45:47]: test dh-golang-autopkgtest: [---
[info] Testing github.com/c-bata/go-prompt...
[info] Source code installed by binary package, overriding
dh_auto_configure...
dh build --buildsystem=golang --with=golang
   dh_update_autotools_config -O--buildsystem=golang
   dh_autoreconf -O--buildsystem=golang
   debian/rules override_dh_auto_configure
make[1]: Entering directory
'/tmp/autopkgtest-lxc.wizha90b/downtmp/autopkgtest_tmp'
mkdir -p "obj-x86_64-linux-gnu"
cp -a /usr/share/gocode/src "obj-x86_64-linux-gnu"
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.wizha90b/downtmp/autopkgtest_tmp'
   dh_auto_build -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install -trimpath -v -p 48
github.com/c-bata/go-prompt github.com/c-bata/go-prompt/completer
internal/unsafeheader
internal/race
math/bits
unicode/utf8
runtime/internal/sys
golang.org/x/sys/internal/unsafeheader
runtime/cgo
sync/atomic
unicode
internal/cpu
runtime/internal/atomic
runtime/internal/math
internal/bytealg
internal/testlog
math
runtime
internal/reflectlite
sync
errors
sort
internal/oserror
io
strconv
syscall
bytes
strings
reflect
regexp/syntax
internal/syscall/unix
internal/syscall/execenv
time
regexp
internal/poll
internal/fmtsort
encoding/binary
os
golang.org/x/sys/unix
os/signal
github.com/mattn/go-runewidth
path/filepath
fmt
io/ioutil
github.com/pkg/term/termios
log
os/user
github.com/c-bata/go-prompt
# github.com/c-bata/go-prompt
src/github.com/c-bata/go-prompt/input_posix.go:67:45: cannot use
&t.origTermios (type *unix.Termios) as type *syscall.Termios in argument
to termios.Tcgetattr
src/github.com/c-bata/go-prompt/input_posix.go:75:52: cannot use &n
(type *unix.Termios) as type *syscall.Termios in argument to
termios.Tcsetattr
src/github.com/c-bata/go-prompt/input_posix.go:83:59: cannot use
&t.origTermios (type *unix.Termios) as type *syscall.Termios in argument
to termios.Tcsetattr
dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v
-p 48 github.com/c-bata/go-prompt github.com/c-bata/go-prompt/completer
returned exit code 2
make: *** [debian/rules:4: build] Error 25
autopkgtest [17:45:52]: test dh-golang-autopkgtest: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: golang-github-c-bata-go-prompt
Source-Version: 0.2.5-1
Done: Anthony Fok 

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

Bug#973205: Not able to reproduce

[Ruben Undheim]

Hi,

I am not able to reproduce the FTBFS with cowbuilder. It builds just fine
on my side.

Would it be possible to try the rebuild again?


Best regards
Ruben

Bug#974563: corosync unable to communicate with pacemaker 1.1.16-1+deb9u1 which contains the fix for CVE-2020-25654

[Markus Koschany]

Am Donnerstag, den 12.11.2020, 15:50 -0300 schrieb Alejandro Taboada:
> Hi !
> 
> Just tested v1.1 and the issue persists. The problem is quiet local
> connection when using with corosync

Hello,

I believe I have found and fixed the problem. The refactored code in lrmd.c
caused the regression. Since this commit is not strictly needed to fix CVE-
2020-25654, I have reverted the changes. On my local setup I don't see any
error messages but I would appreciate a final test from you before I upload to
rule out other possible issues. New source and binary packages are available at

https://people.debian.org/~apo/lts/pacemaker/

Regards,

Markus


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

Bug#974552: upgrade-reports: libc6/libcrypt split breaks perl during buster->bullseye upgrade

[Sven Joachim]

On 2020-11-13 18:23 +0100, Niels Thykier wrote:

> Control: reassign -1 perl-base
> Control: affects -1 upgrade-reports
> Control: severity -1 grave
>
> Hi Perl team,
>
> I have reassigned this bug to perl because perl-base being essential
> must remain functional during an upgrade and AFAICT perl-base fails in
> this case here.
>
> If it is a direct linkage, then you might be needing a Pre-Depends.  If
> it is an indirect linkage then I am not sure how to fix it. :-/

I don't think perl-base is doing anything wrong here, it already uses
Pre-Depends.  AFAICS the problem is that libcrypt.so.1 can temporarily
go missing if libc6 2.31-4 is unpacked before libcrypt1, breaking the
assumption that binaries from essential packages are always usable.

I don't have a good idea how to fix that, though. :-(

Cheers,
   Sven

> Alois Wohlschlager:
>> Package: upgrade-reports
>> Severity: critical
>> Justification: breaks the whole system
>> X-Debbugs-Cc: alo...@gmx-topmail.de
>> 
>> Dear Maintainer,
>> 
>> *** Reporter, please consider answering these questions, where appropriate 
>> ***
>> 
>>* What led up to the situation?
>> 
>>Do an upgrade from buster to bullseye.
>> 
>> 
>>* What exactly did you do (or not do) that was effective (or
>>  ineffective)?
>> 
>>1. adjust sources.list
>>2. apt upgrade
>>3. apt dist-upgrade
>> 
>>* What was the outcome of this action?
>> 
>>apt dist-upgrade goes horribly wrong. Excerpt from the log:
>> 
>> ---
>> Entpacken von libc6:amd64 (2.31-4) über (2.28-10) ...
>> Vormals nicht ausgewähltes Paket libc6:i386 wird gewählt.
>> Vorbereitung zum Entpacken von .../4-libc6_2.31-4_i386.deb ...
>> Entpacken von libc6:i386 (2.31-4) ...
>> Vormals nicht ausgewähltes Paket libgcc-s1:i386 wird gewählt.
>> Vorbereitung zum Entpacken von .../5-libgcc-s1_10.2.0-16_i386.deb ...
>> Entpacken von libgcc-s1:i386 (10.2.0-16) ...
>> Vormals nicht ausgewähltes Paket gcc-10-base:i386 wird gewählt.
>> Vorbereitung zum Entpacken von .../6-gcc-10-base_10.2.0-16_i386.deb ...
>> Entpacken von gcc-10-base:i386 (10.2.0-16) ...
>> /usr/bin/perl: error while loading shared libraries: libcrypt.so.1: cannot 
>> open
>> shared object file: No such file or directory
>> dpkg: Fehler: Fehler beim Ausführen des Hooks »if [ -x /usr/share/debian-
>> security-support/check-support-status.hook ] ; then /usr/sh
>> are/debian-security-support/check-support-status.hook ; fi«, Exitkode 32512
>> ---
>> 
>>At this point, perl is still the version from buster, and libcrypt1 is not
>> yet installed. The missing libcrypt.so.1 also completely breaks PAM, so login
>> and sudo don't work any more.
>>To recover from this outcome, I had to boot with "init=/bin/sh", install 
>> the
>> libcrypt1 package with dpkg and run "apt -f install" twice. This rendered the
>> system operational again and a further "apt dist-upgrade" ran through 
>> smoothly.
>> 
>>* What outcome did you expect instead?
>> 
>>libcrypt1 is installed before libcrypt.so.1 is required again, so the 
>> dist-
>> upgrade can proceed normally.
>> 
>> [...]

Processed: Re: Bug#974177: Info received (serious)

[Debian Bug Tracking System]

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

> severity 974177 important
Bug #974177 [libnss3] libnss3: Handshake failed (-12251) with Pidgin since 
2:3.58-1
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#957369: marked as done (ipband: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Fri, 13 Nov 2020 19:48:28 +
with message-id 
and subject line Bug#957369: fixed in ipband 0.8.1-5.1
has caused the Debian Bug report #957369,
regarding ipband: 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.)


-- 
957369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ipband
Version: 0.8.1-5
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/ipband_0.8.1-5_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

[...]
/usr/bin/ld: popen.o:./ipband.h:182: multiple definition of `started_m'; 
main.o:./ipband.h:182: first defined here
/usr/bin/ld: popen.o:./ipband.h:181: multiple definition of `pcapoffset_m'; 
main.o:./ipband.h:181: first defined here
/usr/bin/ld: popen.o:./ipband.h:180: multiple definition of `pcapfile_m'; 
main.o:./ipband.h:180: first defined here
/usr/bin/ld: popen.o:./ipband.h:179: multiple definition of `pcapdev_m'; 
main.o:./ipband.h:179: first defined here
/usr/bin/ld: popen.o:./ipband.h:178: multiple definition of `preload_m'; 
main.o:./ipband.h:178: first defined here
/usr/bin/ld: popen.o:./ipband.h:177: multiple definition of `isig_m'; 
main.o:./ipband.h:177: first defined here
/usr/bin/ld: reports.o:./ipband.h:184: multiple definition of `ll_tcp_cache'; 
main.o:./ipband.h:184: first defined here
/usr/bin/ld: reports.o:./ipband.h:185: multiple definition of `ll_udp_cache'; 
main.o:./ipband.h:185: first defined here
/usr/bin/ld: reports.o:./ipband.h:203: multiple definition of `mailto_m'; 
main.o:./ipband.h:203: first defined here
/usr/bin/ld: reports.o:./ipband.h:192: multiple definition of `repfname_m'; 
main.o:./ipband.h:192: first defined here
/usr/bin/ld: reports.o:./ipband.h:204: multiple definition of `mailfoot_m'; 
main.o:./ipband.h:204: first defined here
/usr/bin/ld: reports.o:./ipband.h:205: multiple definition of `mtastring_m'; 
main.o:./ipband.h:205: first defined here
/usr/bin/ld: reports.o:./ipband.h:201: multiple definition of `top_m'; 
main.o:./ipband.h:201: first defined here
/usr/bin/ld: reports.o:./ipband.h:206: multiple definition of `report_aggr_m'; 
main.o:./ipband.h:206: first defined here
/usr/bin/ld: reports.o:./ipband.h:178: multiple definition of `preload_m'; 
main.o:./ipband.h:178: first defined here
/usr/bin/ld: reports.o:./ipband.h:182: multiple definition of `started_m'; 
main.o:./ipband.h:182: first defined here
/usr/bin/ld: reports.o:./ipband.h:193: multiple definition of `htmlfname_m'; 
main.o:./ipband.h:193: first defined here
/usr/bin/ld: reports.o:./ipband.h:210: multiple definition of `lenadj_m'; 
main.o:./ipband.h:210: first defined here
/usr/bin/ld: reports.o:./ipband.h:209: multiple definition of `niplist_m'; 
main.o:./ipband.h:209: first defined here
/usr/bin/ld: reports.o:./ipband.h:208: multiple definition of `iplist_m'; 
main.o:./ipband.h:208: first defined here
/usr/bin/ld: reports.o:./ipband.h:207: multiple definition of `promisc_m'; 
main.o:./ipband.h:207: first defined here
/usr/bin/ld: reports.o:./ipband.h:202: multiple definition of `config_m'; 
main.o:./ipband.h:202: first defined here
/usr/bin/ld: reports.o:./ipband.h:200: multiple definition of `fork_m'; 
main.o:./ipband.h:200: first defined here
/usr/bin/ld: reports.o:./ipband.h:199: multiple definition of `thresh_m'; 
main.o:./ipband.h:199: first defined here
/usr/bin/ld: reports.o:./ipband.h:197: multiple definition of `rcycle_m'; 
main.o:./ipband.h:197: f

Bug#974177: Info received (serious)

[VA]

severity 974177 important
thanks

Oops, I thought the bug was on the pidgin package, sorry.

Processed: Re: Bug#974177: Info received (serious)

[Debian Bug Tracking System]

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

> severity 974177 serious
Bug #974177 [libnss3] libnss3: Handshake failed (-12251) with Pidgin since 
2:3.58-1
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Bug#974686: python3-blockdev: Missing dependencies, without deps to gir1.2-blockdev-2.0 the python module in unsable

[Jean-Yves NOLEN]

Package: python3-blockdev
Version: 2.20-7+deb10u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

What's need to be done:
- Play arround with the BlockDev API within python

What exactly did you do (or not do) that was effective (or ineffective)?
- Do a simple apt install python3-blockdev and install with deps
- Run this piece of code with the offcial pyobject docs as reference 
  - 

=== Python Source ===
import gi
from gi import Repository
version = Repository.get_default().enumerate_versions("BlockDev")
gi.require_version("BlockDev", version[0] if version else "2.0")
from gi.repository import BlockDev
print(BlockDev.__name__)
===

What was the outcome of this action?

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Blockdev not available

* What outcome did you expect instead?

gi.repository.BlockDev to stdout

* Found Workarround:

Run apt install gir1.2-blockdev-2.0 install with deps and rerun the python 
snippet

* Proposed Solution:
Make python3-blockdev depends on gir1.2-blockdev-2.0 OR maka a reference in 
suggested package


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

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

Versions of packages python3-blockdev depends on:
ii  libblockdev2  2.20-7+deb10u1
ii  python3   3.7.3-1
ii  python3-gi3.30.4-1

python3-blockdev recommends no packages.

python3-blockdev suggests no packages.

-- no debconf information

Bug#974619: marked as done (FTBFS on mips*el: ../src/basic/macro.h:415:9: error: static assertion failed: "__NR_close_range == systemd_NR_close_range")

[Debian Bug Tracking System]

Your message dated Fri, 13 Nov 2020 18:48:32 +
with message-id 
and subject line Bug#974619: fixed in systemd 247~rc2-2
has caused the Debian Bug report #974619,
regarding FTBFS on mips*el: ../src/basic/macro.h:415:9: error: static assertion 
failed: "__NR_close_range == systemd_NR_close_range"
to be marked as done.

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

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


-- 
974619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: systemd
Version: 247~rc2-1
Severity: serious
User: debian-m...@lists.debian.org
Usertags: mipsel
X-Debbugs-Cc: debian-m...@lists.debian.org

Hi mips porters,

systemd in experimental FTBFS on mipsel and mips64el
https://buildd.debian.org/status/fetch.php?pkg=systemd&arch=mips64el&ver=247%7Erc2-1&stamp=1605223087&raw=0
https://buildd.debian.org/status/fetch.php?pkg=systemd&arch=mipsel&ver=247%7Erc2-1&stamp=1605222663&raw=0

[56/2002] cc -Isrc/basic/libbasic.a.p -Isrc/basic -I../src/basic -Isrc/boot 
-I../src/boot -Isrc/core -I../src/core -Isrc/home -I../src/home -Isrc/journal 
-I../src/journal -Isrc/journal-remote -I../src/journal-remote 
-Isrc/libsystemd-network -I../src/libsystemd-network -I../src/libsystemd/sd-bus 
-I../src/libsystemd/sd-device -I../src/libsystemd/sd-event 
-I../src/libsystemd/sd-hwdb -I../src/libsystemd/sd-id128 
-I../src/libsystemd/sd-netlink -I../src/libsystemd/sd-network 
-I../src/libsystemd/sd-resolve -Isrc/libudev -I../src/libudev -Isrc/login 
-I../src/login -Isrc/nspawn -I../src/nspawn -Isrc/resolve -I../src/resolve 
-Isrc/shared -I../src/shared -Isrc/shutdown -I../src/shutdown -Isrc/systemd 
-I../src/systemd -I../src/time-wait-sync -Isrc/timesync -I../src/timesync 
-Isrc/udev -I../src/udev -I../src/xdg-autostart-generator -I. -I.. -flto 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-Wextra -std=gnu99 -Wno-unused-parameter -Wno-missing-field-initializers 
-Wno-unused-result -Wno-format-signedness -Werror=undef -Wlogical-op 
-Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self 
-Wfloat-equal -Wsuggest-attribute=noreturn -Werror=missing-prototypes 
-Werror=implicit-function-declaration -Werror=missing-declarations 
-Werror=return-type -Werror=incompatible-pointer-types -Werror=format=2 
-Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn 
-Wimplicit-fallthrough=5 -Wshadow -Wendif-labels -Wstrict-aliasing=2 
-Wwrite-strings -Werror=overflow -Werror=shift-count-overflow 
-Werror=shift-overflow=2 -Wdate-time -Wnested-externs -Wno-maybe-uninitialized 
-ffast-math -fno-common -fdiagnostics-show-option -fno-strict-aliasing 
-fvisibility=hidden -fstack-protector -fstack-protector-strong 
--param=ssp-buffer-size=4 -ffunction-sections -fdata-sections -Werror=shadow 
-include config.h -g -O2 '-fdebug-prefix-map=/<>=.' 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -fvisibility=default -MD -MQ 
src/basic/libbasic.a.p/fd-util.c.o -MF src/basic/libbasic.a.p/fd-util.c.o.d -o 
src/basic/libbasic.a.p/fd-util.c.o -c ../src/basic/fd-util.c
FAILED: src/basic/libbasic.a.p/fd-util.c.o
cc -Isrc/basic/libbasic.a.p -Isrc/basic -I../src/basic -Isrc/boot -I../src/boot 
-Isrc/core -I../src/core -Isrc/home -I../src/home -Isrc/journal 
-I../src/journal -Isrc/journal-remote -I../src/journal-remote 
-Isrc/libsystemd-network -I../src/libsystemd-network -I../src/libsystemd/sd-bus 
-I../src/libsystemd/sd-device -I../src/libsystemd/sd-event 
-I../src/libsystemd/sd-hwdb -I../src/libsystemd/sd-id128 
-I../src/libsystemd/sd-netlink -I../src/libsystemd/sd-network 
-I../src/libsystemd/sd-resolve -Isrc/libudev -I../src/libudev -Isrc/login 
-I../src/login -Isrc/nspawn -I../src/nspawn -Isrc/resolve -I../src/resolve 
-Isrc/shared -I../src/shared -Isrc/shutdown -I../src/shutdown -Isrc/systemd 
-I../src/systemd -I../src/time-wait-sync -Isrc/timesync -I../src/timesync 
-Isrc/udev -I../src/udev -I../src/xdg-autostart-generator -I. -I.. -flto 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-Wextra -std=gnu99 -Wno-unused-parameter -Wno-missing-field-initializers 
-Wno-unused-result -Wno-format-signedness -Werror=undef -Wlogical-op 
-Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self 
-Wfloat-equal -Wsuggest-attribute=noreturn -Werror=missing-prototypes 
-Werror=implicit-function-declaration -Werror=missing-declarations 
-Werror=return-type -Werror=incompatible-pointer-types -Werror=format=2 
-Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn 
-Wimplicit-fallthrough=5 -Wshadow -W

Processed: Bug#973126 marked as pending in responses

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #973126 [src:responses] responses: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
Added tag(s) pending.

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

Bug#973126: marked as pending in responses

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #973126 in responses 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/responses/-/commit/a6fd876548eb5971f974cfadc4b02e905225c175


New upstream release.

Compatible with Python 3.9.

Closes: #973126.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973126

Bug#974683: trafficserver: autopkgtest uses pip to download and install code from the internet

[Paul Gevers]

Source: trafficserver
Version: 8.1.0+ds-1
Severity: serious
Justification: ftp-master autoreject ruling

Hi,

Your package has an autopkgtest, awesome. However, I noticed that it
installs Python code using pip. Running downloaded code from internet is
not allowed in the Debian archive; see the ftp-masters autoreject list [1].

Downloading data seems to be allowed, but please add a needs-internet
restriction in that case.

Also, your test fails once in a while. Please if you keep it after the
above, make it more robust against network issues.

Paul

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


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

https://ci.debian.net/data/autopkgtest/testing/arm64/t/trafficserver/8149771/log.gz

env-test/bin/pip install autest==1.8.0 hyper requests dnslib httpbin
gunicorn traffic-replay
Collecting autest==1.8.0
  Downloading autest-1.8.0-py3-none-any.whl (138 kB)
Collecting hyper
  Downloading hyper-0.7.0-py2.py3-none-any.whl (269 kB)
Collecting requests
  Downloading requests-2.25.0-py2.py3-none-any.whl (61 kB)
Collecting dnslib
  Downloading dnslib-0.9.14.tar.gz (72 kB)
Collecting httpbin
  Downloading httpbin-0.7.0-py2.py3-none-any.whl (86 kB)
Collecting gunicorn
  Downloading gunicorn-20.0.4-py2.py3-none-any.whl (77 kB)
Collecting traffic-replay
  Downloading traffic_replay-1.0.0-py3-none-any.whl (25 kB)
Collecting future
  Downloading future-0.18.2.tar.gz (829 kB)
Collecting psutil
  Downloading psutil-5.7.3.tar.gz (465 kB)
Collecting colorama
  Downloading colorama-0.4.4-py2.py3-none-any.whl (16 kB)
Collecting h2<3.0,>=2.4
  Downloading h2-2.6.2-py2.py3-none-any.whl (71 kB)
Collecting hyperframe<4.0,>=3.2
  Downloading hyperframe-3.2.0-py2.py3-none-any.whl (13 kB)
Collecting chardet<4,>=3.0.2
  Downloading chardet-3.0.4-py2.py3-none-any.whl (133 kB)
Collecting certifi>=2017.4.17
  Downloading certifi-2020.11.8-py2.py3-none-any.whl (155 kB)
Collecting urllib3<1.27,>=1.21.1
  Downloading urllib3-1.26.2-py2.py3-none-any.whl (136 kB)
Collecting idna<3,>=2.5
  Downloading idna-2.10-py2.py3-none-any.whl (58 kB)
Collecting six
  Downloading six-1.15.0-py2.py3-none-any.whl (10 kB)
Collecting Flask
  Downloading Flask-1.1.2-py2.py3-none-any.whl (94 kB)
Collecting brotlipy
  Downloading brotlipy-0.7.0.tar.gz (413 kB)
ERROR: Command errored out with exit status 1:
 command:
/tmp/autopkgtest-lxc.dz4jb_fv/downtmp/build.51D/src/tests/env-test/bin/python
-c 'import sys, setuptools, tokenize; sys.argv[0] =
'"'"'/tmp/pip-install-aze8omd7/brotlipy/setup.py'"'"';
__file__='"'"'/tmp/pip-install-aze8omd7/brotlipy/setup.py'"'"';f=getattr(tokenize,
'"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"',
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))'
egg_info --egg-base /tmp/pip-pip-egg-info-7_jpp5o4
 cwd: /tmp/pip-install-aze8omd7/brotlipy/
Complete output (32 lines):
ERROR: Could not find a version that satisfies the requirement
cffi>=1.0.0 (from versions: none)



signature.asc
Description: OpenPGP digital signature

Processed: Bug#974538 marked as pending in kscreenlocker

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #974538 [libkscreenlocker5] libkscreenlocker5: kwin cannot start due to 
missing libkscreenunlocker5 symbols
Added tag(s) pending.

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

Bug#974538: marked as pending in kscreenlocker

[Scarlett Gately Moore]

Control: tag -1 pending

Hello,

Bug #974538 in kscreenlocker 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/kde/kscreenlocker/-/commit/5b5d09c5a06caa20d0b94d225a6a9c7725943887


Fix "kwin cannot start due to missing libkscreenunlocker5 symbols"
A symbols file was introduced this release in packaging,
in transition an ABI breakage was exposed in kwin-common.
To resolve: added a Breaks to kwin-common < this release
to ensure the new version is installed to avoid the
ABI breakage. Thanks to Norb for suggestion. (Closes: #974538)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/974538

Bug#974552: upgrade-reports: libc6/libcrypt split breaks perl during buster->bullseye upgrade

[Niels Thykier]

Control: reassign -1 perl-base
Control: affects -1 upgrade-reports
Control: severity -1 grave

Hi Perl team,

I have reassigned this bug to perl because perl-base being essential
must remain functional during an upgrade and AFAICT perl-base fails in
this case here.

If it is a direct linkage, then you might be needing a Pre-Depends.  If
it is an indirect linkage then I am not sure how to fix it. :-/

~Niels

Alois Wohlschlager:
> Package: upgrade-reports
> Severity: critical
> Justification: breaks the whole system
> X-Debbugs-Cc: alo...@gmx-topmail.de
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> 
>Do an upgrade from buster to bullseye.
> 
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
>1. adjust sources.list
>2. apt upgrade
>3. apt dist-upgrade
> 
>* What was the outcome of this action?
> 
>apt dist-upgrade goes horribly wrong. Excerpt from the log:
> 
> ---
> Entpacken von libc6:amd64 (2.31-4) über (2.28-10) ...
> Vormals nicht ausgewähltes Paket libc6:i386 wird gewählt.
> Vorbereitung zum Entpacken von .../4-libc6_2.31-4_i386.deb ...
> Entpacken von libc6:i386 (2.31-4) ...
> Vormals nicht ausgewähltes Paket libgcc-s1:i386 wird gewählt.
> Vorbereitung zum Entpacken von .../5-libgcc-s1_10.2.0-16_i386.deb ...
> Entpacken von libgcc-s1:i386 (10.2.0-16) ...
> Vormals nicht ausgewähltes Paket gcc-10-base:i386 wird gewählt.
> Vorbereitung zum Entpacken von .../6-gcc-10-base_10.2.0-16_i386.deb ...
> Entpacken von gcc-10-base:i386 (10.2.0-16) ...
> /usr/bin/perl: error while loading shared libraries: libcrypt.so.1: cannot 
> open
> shared object file: No such file or directory
> dpkg: Fehler: Fehler beim Ausführen des Hooks »if [ -x /usr/share/debian-
> security-support/check-support-status.hook ] ; then /usr/sh
> are/debian-security-support/check-support-status.hook ; fi«, Exitkode 32512
> ---
> 
>At this point, perl is still the version from buster, and libcrypt1 is not
> yet installed. The missing libcrypt.so.1 also completely breaks PAM, so login
> and sudo don't work any more.
>To recover from this outcome, I had to boot with "init=/bin/sh", install 
> the
> libcrypt1 package with dpkg and run "apt -f install" twice. This rendered the
> system operational again and a further "apt dist-upgrade" ran through 
> smoothly.
> 
>* What outcome did you expect instead?
> 
>libcrypt1 is installed before libcrypt.so.1 is required again, so the dist-
> upgrade can proceed normally.
> 
> [...]

Processed: Re: Bug#974552: upgrade-reports: libc6/libcrypt split breaks perl during buster->bullseye upgrade

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 perl-base
Bug #974552 [upgrade-reports] upgrade-reports: libc6/libcrypt split breaks perl 
during buster->bullseye upgrade
Bug reassigned from package 'upgrade-reports' to 'perl-base'.
Ignoring request to alter found versions of bug #974552 to the same values 
previously set
Ignoring request to alter fixed versions of bug #974552 to the same values 
previously set
> affects -1 upgrade-reports
Bug #974552 [perl-base] upgrade-reports: libc6/libcrypt split breaks perl 
during buster->bullseye upgrade
Added indication that 974552 affects upgrade-reports
> severity -1 grave
Bug #974552 [perl-base] upgrade-reports: libc6/libcrypt split breaks perl 
during buster->bullseye upgrade
Severity set to 'grave' from 'critical'

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

Bug#973147: pg-wait-sampling

[Krüger]

The new release 1.1.2 should fix the bug:

https://github.com/postgrespro/pg_wait_sampling/releases

Bug#973129: marked as done (pglogical: FTBFS: ld: cannot find -lreadline)

[Debian Bug Tracking System]

Your message dated Fri, 13 Nov 2020 14:46:01 +
with message-id 
and subject line Bug#973129: fixed in pglogical 2.3.3-2
has caused the Debian Bug report #973129,
regarding pglogical: FTBFS: ld: cannot find -lreadline
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.)


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

Hi,

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

Relevant part (hopefully):
> gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement 
> -Werror=vla -Wendif-labels -Wmissing-format-attribute 
> -Wimplicit-fallthrough=3 -Wformat-security -fno-strict-aliasing -fwrapv 
> -fexcess-precision=standard -Wno-format-truncation -Wno-stringop-truncation 
> -g -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -fno-omit-frame-pointer -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC -fPIC 
> pglogical_create_subscriber.o pglogical_fe.o -L/usr/lib/x86_64-linux-gnu  
> -Wl,-z,relro -Wl,-z,now -L/usr/lib/llvm-11/lib  -Wl,--as-needed -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security  -L/usr/lib/postgresql/13/lib -lpgcommon -lpgport 
> -L/usr/lib/x86_64-linux-gnu -lpq -lpgcommon -lpgport -lpthread -lselinux 
> -lxslt -lxml2 -lpam -lssl -lcrypto -lgssapi_krb5 -lz -lreadline -lrt -ldl -lm 
>  -o pglogical_create_subscriber
> /usr/bin/ld: cannot find -lreadline
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/pglogical_2.3.3-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated pglogical 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: Fri, 13 Nov 2020 15:12:59 +0100
Source: pglogical
Architecture: source
Version: 2.3.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
Changed-By: Christoph Berg 
Closes: 973129
Changes:
 pglogical (2.3.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Add B-D on libreadline-dev as PGXS adds -lreadline, even when it's not
 being used. (Closes: #973129)
Checksums-Sha1:
 7184bc77db863393014f79632040767ae28948f6 2335 pglogical_2.3.3-2.dsc
 1e48546a62a3882d46277af7ddf2a60de4f98116 179252 pglogical_2.3.3-2.debian.tar.xz
Checksums-Sha256:
 e051bad550eef9643647b87674638e550f69bff4c072df001e0560eff6a0b3ab 2335 
pglogical_2.3.3-2.dsc
 bda3b9dbc02cb8378e75f8b2cca11526bea043109d26da3760cddaca7eaf0589 179252 
pglogical_2.3.3-2.debian.tar.xz
Files:
 f3ba250bb3bfa714596bb1afda3221a8 2335 database optional pglogical_2.3.3-2.dsc
 a56e331e0a0885e69bff84d69487ade6 179252 database optional 
pglogical_2.3.3-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl+umroACgkQTFprqxLS
p66qWQ//eyQYc9u6mEvISB/tNQVAoEzloHt9NZpDtsX7DLqJ3ACPWoeRZJNORXHo
uxectrbG/GSlH/odi06u9EDTnBaDAKEv5i+ntHkEojapX70cQ7TCMDkDqxNzKuTH
TIbT/5NmGNf5rVSasEt3mbbRZCR1ZM84dEuiiX90EzV81JVr6eyeVUMysJApz5jw
d2qqOeJ15BZixsY/Xs1CmdTutZkfKXdWSBhJS3Bpl1U0mnMQH6S5w47guap4+Ueo
254Lg7jQbks/D5n0/bc2j5XLOC0wZx44Ws/yVwizXEmU4p/R1Mmyrxdym4BOfMHq
V4E2j93i9/hY2EtTmqL30Z530DsJ98Mhz1ZaI9hO8wRtREqOA4ZfTtWWm8U2LPLr
y3THbsY1pt8lkcJfDcz9r/OKeMUaA+zDtNQKCYgYJJXyjJWLu1Z21gSVosLJcZf

Bug#974666: Acknowledgement (gnome-sound-recorder: The export file dialog disappears suddendly after a few seconds.)

[Sergio Costas]

Also comment that this bug doesn't happen when the program is run as a 
flatpak, only when run as a native program.


El 13/11/20 a las 15:15, Debian Bug Tracking System escribió:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 974666: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974666.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
   rasters...@gmail.com
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
  Debian GNOME Maintainers 

If you wish to submit further information on this problem, please
send it to 974...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

Processed: Bug#973129 marked as pending in pglogical

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #973129 [src:pglogical] pglogical: FTBFS: ld: cannot find -lreadline
Added tag(s) pending.

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

Bug#973129: marked as pending in pglogical

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #973129 in pglogical 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/postgresql/pglogical/-/commit/fb637b5dfef2228a666be59fc52adc93d295e7f7


Add B-D on libreadline-dev as PGXS adds -lreadline, even when it's not being 
used.

(Closes: #973129)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973129

Bug#974666: gnome-sound-recorder: The export file dialog disappears suddendly after a few seconds.

[raster]

Package: gnome-sound-recorder
Version: 3.38.0-1
Severity: grave
Tags: patch
Justification: causes non-serious data loss
X-Debbugs-Cc: rasters...@gmail.com

Dear Maintainer,

After doing a recording, pressing the "export" button shows, as expected, a
file dialog to choose where to export the file. The problem is that the
dialog disappears sudendly after some seconds (a variable number: sometimes
as soon as three-four seconds, others between ten and twelve seconds). To
trigger this bug, just press the "export" button and wait.

This is critical because if the user want to navigate to a folder and uses too
much time, the dialog closes before being able to do the operation.

This seems a problem with the garbage collector. I attach a patch that fixes
it.



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

Kernel: Linux 5.9.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-sound-recorder depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-1
ii  gir1.2-gdkpixbuf-2.0 2.40.0+dfsg-5
ii  gir1.2-glib-2.0  1.66.1-1
ii  gir1.2-gst-plugins-bad-1.0   1.18.1-1
ii  gir1.2-gst-plugins-base-1.0  1.18.1-1
ii  gir1.2-gstreamer-1.0 1.18.1-1
ii  gir1.2-gtk-3.0   3.24.23-2
ii  gir1.2-handy-1   1.0.1-1
ii  gir1.2-pango-1.0 1.46.2-3
ii  gjs  1.66.1-1
ii  gstreamer1.0-plugins-base1.18.1-1
ii  gstreamer1.0-plugins-good1.18.1-1
ii  gstreamer1.0-pulseaudio  1.18.1-1

gnome-sound-recorder recommends no packages.

gnome-sound-recorder suggests no packages.

-- no debconf information
diff --git a/src/row.js b/src/row.js
index 154c0ef..743de63 100644
--- a/src/row.js
+++ b/src/row.js
@@ -68,16 +68,17 @@ var Row = GObject.registerClass({
 let exportAction = new Gio.SimpleAction({ name: 'export' });
 exportAction.connect('activate', () => {
 const window = Gio.Application.get_default().get_active_window();
-const dialog = Gtk.FileChooserNative.new(_('Export Recording'), 
window, Gtk.FileChooserAction.SAVE, _('_Export'), _('_Cancel'));
-
dialog.set_current_name(`${this._recording.name}.${this._recording.extension}`);
-dialog.connect('response', (_dialog, response) => {
+this.exportDialog = Gtk.FileChooserNative.new(_('Export 
Recording'), window, Gtk.FileChooserAction.SAVE, _('_Export'), _('_Cancel'));
+
this.exportDialog.set_current_name(`${this._recording.name}.${this._recording.extension}`);
+this.exportDialog.connect('response', (_dialog, response) => {
 if (response === Gtk.ResponseType.ACCEPT) {
-const dest = dialog.get_file();
+const dest = this.exportDialog.get_file();
 this._recording.save(dest);
 }
-dialog.destroy();
+this.exportDialog.destroy();
+this.exportDialog = null;
 });
-dialog.show();
+this.exportDialog.show();
 });
 this.actionGroup.add_action(exportAction);
 

Processed: tagging 958610, tagging 958592

[Debian Bug Tracking System]

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

> tags 958610 + pending
Bug #958610 [src:open-iscsi] open-iscsi: Build-Depends on deprecated dh-systemd 
which is going away
Added tag(s) pending.
> tags 958592 + pending
Bug #958592 [src:open-isns] open-isns: Build-Depends on deprecated dh-systemd 
which is going away
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#958592: open-isns: Build-Depends on deprecated dh-systemd which is going away

[Michael Biebl]

On Thu, 23 Apr 2020 22:37:30 +0200 bi...@debian.org wrote:
> Source: open-isns
> Severity: normal
> User: pkg-systemd-maintain...@lists.alioth.debian.org
> Usertags: dh-systemd-removal
> 
> Hi,
> 
> your package open-isns declares a build dependency on dh-systemd.
> dh-systemd was merged into debhelper in version 9.20160709 [1] and
since
> stretch, dh-systemd is an empty transitional package.
> 
> For bullseye we intend to drop this empty transitional package.
> 
> Once we drop dh-systemd, this bug report will become RC.
> 
> Please update your package accordingly. The change should be as
simple as
> replacing the build dependency on dh-systemd with a build dependency
on
> debhelper (>= 9.20160709).
> 
> Regards,
> Michael
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670

I've uploaded a minimal fix to DELAYED/3
The package already had a Build-Depends on debhelper >= 10, so dh-
systemd could simply be removed without requiring further changes.

Debdiff is attached.

Regards,
Michael
diff -Nru open-isns-0.97/debian/changelog open-isns-0.97/debian/changelog
--- open-isns-0.97/debian/changelog	2018-10-07 08:08:11.0 +0200
+++ open-isns-0.97/debian/changelog	2020-11-13 14:55:50.0 +0100
@@ -1,3 +1,10 @@
+open-isns (0.97-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop Build-Depends on obsolete dh-systemd (Closes: #958592)
+
+ -- Michael Biebl   Fri, 13 Nov 2020 14:55:50 +0100
+
 open-isns (0.97-3) unstable; urgency=medium
 
   [ Ritesh Raj Sarraf ]
diff -Nru open-isns-0.97/debian/control open-isns-0.97/debian/control
--- open-isns-0.97/debian/control	2018-10-07 08:07:36.0 +0200
+++ open-isns-0.97/debian/control	2020-11-13 14:55:41.0 +0100
@@ -6,7 +6,6 @@
Christian Seiler 
 Build-Depends: debhelper (>= 10~),
dh-exec,
-   dh-systemd,
libssl-dev,
po-debconf
 Standards-Version: 3.9.8


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

Bug#958610: open-iscsi: Build-Depends on deprecated dh-systemd which is going away

[Michael Biebl]

On Thu, 23 Apr 2020 22:37:30 +0200 bi...@debian.org wrote:
> Source: open-iscsi
> Severity: normal
> User: pkg-systemd-maintain...@lists.alioth.debian.org
> Usertags: dh-systemd-removal
> 
> Hi,
> 
> your package open-iscsi declares a build dependency on dh-systemd.
> dh-systemd was merged into debhelper in version 9.20160709 [1] and
since
> stretch, dh-systemd is an empty transitional package.
> 
> For bullseye we intend to drop this empty transitional package.
> 
> Once we drop dh-systemd, this bug report will become RC.
> 
> Please update your package accordingly. The change should be as
simple as
> replacing the build dependency on dh-systemd with a build dependency
on
> debhelper (>= 9.20160709).
> 
> Regards,
> Michael
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670
> 
> 
> 

I uploaded a fix for that to DELAYED/3.

It contains a bit of a hack: To make it build, I temporarily switched
back to gcc-9. This is not a proper fix for #957630 but I wanted to
keep the debdiff minimal (see attached)

Regards,
Michael
diff -Nru open-iscsi-2.0.874/debian/changelog open-iscsi-2.0.874/debian/changelog
--- open-iscsi-2.0.874/debian/changelog	2018-12-12 01:05:19.0 +0100
+++ open-iscsi-2.0.874/debian/changelog	2020-11-13 14:10:09.0 +0100
@@ -1,3 +1,12 @@
+open-iscsi (2.0.874-7.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Build-Depends to use debhelper (>= 9.20160709) instead of
+dh-systemd. (Closes: #958610)
+  * Temporarily switch to gcc-9 to workaround a build failure with gcc-10.
+
+ -- Michael Biebl   Fri, 13 Nov 2020 14:10:09 +0100
+
 open-iscsi (2.0.874-7.1) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru open-iscsi-2.0.874/debian/control open-iscsi-2.0.874/debian/control
--- open-iscsi-2.0.874/debian/control	2018-12-12 01:05:19.0 +0100
+++ open-iscsi-2.0.874/debian/control	2020-11-13 14:10:09.0 +0100
@@ -5,12 +5,12 @@
 Uploaders: Ritesh Raj Sarraf ,
Christian Seiler 
 Build-Depends: autotools-dev,
+   gcc-9,
bison,
bzip2,
-   debhelper (>= 9),
+   debhelper (>= 9.20160709),
dh-autoreconf,
dh-exec,
-   dh-systemd,
dpkg-dev (>= 1.16.1~),
flex,
libisns-dev (>= 0.96-4~),
diff -Nru open-iscsi-2.0.874/debian/rules open-iscsi-2.0.874/debian/rules
--- open-iscsi-2.0.874/debian/rules	2018-12-11 19:05:42.0 +0100
+++ open-iscsi-2.0.874/debian/rules	2020-11-13 14:10:09.0 +0100
@@ -5,6 +5,10 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 export DEB_CFLAGS_MAINT_APPEND = -Wall -DOFFLOAD_BOOT_SUPPORTED
 
+# This is a hack and should be removed once
+# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957630 has been fixed properly
+export CC = gcc-9
+
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/default.mk
 


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

Bug#974660: marked as done (ginkgocadx: FTBFS in sid)

[Debian Bug Tracking System]

Your message dated Fri, 13 Nov 2020 13:18:22 +
with message-id 
and subject line Bug#974660: fixed in ginkgocadx 3.8.8-5
has caused the Debian Bug report #974660,
regarding ginkgocadx: FTBFS in sid
to be marked as done.

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

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


-- 
974660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ginkgocadx
Version: 3.8.8-4
Severity: serious

Hello, looks like the current version in sid now FTBFS against new libdcmtk15

can you please have a look?
https://buildd.debian.org/status/fetch.php?pkg=ginkgocadx&arch=amd64&ver=3.8.8-4%2Bb1&stamp=1605242581&raw=0

A snip of the failing log is here:

cd /<>/obj-x86_64-linux-gnu/cadxcore && /usr/bin/c++ -DAPIEXPORT 
-DCURL_STATICLIB -DDCMTK_POST_20170228 -DGINKGO_ARCH_x86_64 
-DGINKGO_CODENAME=\"\" -DGINKGO_VERSION=\"3.8.8\" -DHAVE_CONFIG_H 
-DINTERNET_DIST -DITK_IO_FACTORY_REGISTER_MANAGER -DLINUX -DMONOLITIC 
-DUSE_SYSTEM_SQLITE -DUSING_EXTENSIONS -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 
-D__WXGTK__ -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 -DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpenGL)" 
-I/<>/obj-x86_64-linux-gnu/cadxcore/ITKFactoryRegistration 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gio-unix-2.0 -I/usr/include/pango-1.0 -I/usr/include/fribidi 
-I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libmount -I/usr/include/blkid 
-I/<>/cadxcore/CADxCore -I/<>/cadxcore 
-I/<>/cadxcore/vtk -I/<>/cadxcore/itk 
-I/<>/cadxcore/wx -I/<>/cadxcore/wx/VTK 
-I/<>/cadxcore/VTKInria3D 
-I/<>/cadxcore/VTKInria3D/wxVTK -I/usr/include/jsoncpp 
-I/<>/../lib/Linux-x86_64/libcurl-7.28.1/include 
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0 
-I/usr/include/vtk-6.3 -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/hdf5/openmpi 
-I/usr/include/libxml2 -isystem /usr/include/gdcm-3.0 -isystem 
/usr/include/ITK-4.13 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fPIC   -o 
CMakeFiles/CADxCore.dir/main/controllers/modalitysettingscontroller.cpp.o -c 
/<>/cadxcore/main/controllers/modalitysettingscontroller.cpp
[ 31%] Building CXX object 
cadxcore/CMakeFiles/CADxCore.dir/main/controllers/pacscontroller.cpp.o
cd /<>/obj-x86_64-linux-gnu/cadxcore && /usr/bin/c++ -DAPIEXPORT 
-DCURL_STATICLIB -DDCMTK_POST_20170228 -DGINKGO_ARCH_x86_64 
-DGINKGO_CODENAME=\"\" -DGINKGO_VERSION=\"3.8.8\" -DHAVE_CONFIG_H 
-DINTERNET_DIST -DITK_IO_FACTORY_REGISTER_MANAGER -DLINUX -DMONOLITIC 
-DUSE_SYSTEM_SQLITE -DUSING_EXTENSIONS -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 
-D__WXGTK__ -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 -DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpenGL)" 
-I/<>/obj-x86_64-linux-gnu/cadxcore/ITKFactoryRegistration 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gio-unix-2.0 -I/usr/include/pango-1.0 -I/usr/include/fribidi 
-I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libmount -I/usr/include/blkid 
-I/<>/cadxcore/CADxCore -I/<>/cadxcore 
-I/<>/cadxcore/vtk -I/<>/cadxcore/itk 
-I/<>/cadxcore/wx -I/<>/cadxcore/wx/VTK 
-I/<>/cadxcore/VTKInria3D 
-I/<>/cadxcore/VTKInria3D/wxVTK -I/usr/include/jsoncpp 
-I/<>/../lib/Linux-x86_64/libcurl-7.28.1/include 
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0 

Bug#974660: marked as pending in ginkgocadx

[Gianfranco Costamagna]

Control: tag -1 pending

Hello,

Bug #974660 in ginkgocadx 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/med-team/ginkgocadx/-/commit/ad586a4734a3ef02267b713efe46291f8af51319


Cherry-pick upstream-proposed fix for build failure due to new dcmtk 3.6.5 
(Closes: #974660)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/974660

Processed: Bug#974660 marked as pending in ginkgocadx

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #974660 [src:ginkgocadx] ginkgocadx: FTBFS in sid
Added tag(s) pending.

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

Processed: Re: ginkgocadx: FTBFS in sid

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #974660 [src:ginkgocadx] ginkgocadx: FTBFS in sid
Added tag(s) patch.
> forwarded -1 https://github.com/gerddie/ginkgocadx/pull/53
Bug #974660 [src:ginkgocadx] ginkgocadx: FTBFS in sid
Set Bug forwarded-to-address to 'https://github.com/gerddie/ginkgocadx/pull/53'.

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

Bug#974660: ginkgocadx: FTBFS in sid

[Gianfranco Costamagna]

control: tags -1 patch
control: forwarded -1 https://github.com/gerddie/ginkgocadx/pull/53

https://github.com/gerddie/ginkgocadx/pull/53

I fixed the build failure by adding the missing include, and opened a Pull 
Request upstream.

cheers,

Gianfranco

Bug#968730: SO version specification changed upstream

[Adrian Bunk]

On Tue, Sep 01, 2020 at 12:29:02PM +0200, Michael Hanke wrote:
> It seems that upstream has changed the way they set the SO version
> information:
> 
> https://salsa.debian.org/med-team/nifticlib/-/commit/eabee0938978a7f5e8e28522be3d856dee3975cf#48dc04d58c3c3f29ad0415ca64d38e3231bffd87_0_17
> 
> and the previous explicit set in the top-level CMakeLists.txt is gone.

I just built 3.0.1, which seems to have fixed the breakage:
libniftiio.so.2
libnifticdf.so.2
libznz.so.3

But libznz changed soname, the library package should really be
split into 3 packages and then a transition done for reverse
dependencies to pick up runtime dependencies on the split packages:
libniftiio2
libnifticdf2
libznz3

> Michael Hanke

cu
Adrian

Processed: ginkgocadx: FTBFS in sid

[Debian Bug Tracking System]

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

> tags 974660 + ftbfs
Bug #974660 [src:ginkgocadx] ginkgocadx: FTBFS in sid
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#973919: suckless-tools: dmenu disappears when typing in i3wm

[Tobias Frost]

Control: severity -1 important

On Sat, 07 Nov 2020 14:52:56 +0100 ORL  wrote:
> Package: suckless-tools
> Version: 45-1
> Severity: grave
> Justification: renders package unusable

(well, it makes one command unusable, not the whole package)

I see you have filed #973515; the description of that one reads a bit like
this is the same issue, is it?  (In this case the bugs should be merged
and assigned to the package causing it…)

For sure, this is not a severity-grave bug; I'm reducing the severity
to a more appropiate level.

--
tobi

Processed: Adios FTBFS on python3.9 due to cython

[Debian Bug Tracking System]

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

> retitle 972420   Adios FTBFS with python3.9 due to cython
Bug #972420 [src:adios] adios ignores errors in the packaging and ftbfs with 
python3.9
Changed Bug title to 'Adios FTBFS with python3.9 due to cython' from 'adios 
ignores errors in the packaging and ftbfs with python3.9'.
> clone 972420 -1
Bug #972420 [src:adios] Adios FTBFS with python3.9 due to cython
Bug 972420 cloned as bug 974662
> reassign -1 cython
Bug #974662 [src:adios] Adios FTBFS with python3.9 due to cython
Bug reassigned from package 'src:adios' to 'cython'.
No longer marked as found in versions adios/1.13.1-26.
Ignoring request to alter fixed versions of bug #974662 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Re: suckless-tools: dmenu disappears when typing in i3wm

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #973919 [suckless-tools] suckless-tools: dmenu disappears when typing in 
i3wm
Severity set to 'important' from 'grave'

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

Bug#974660: ginkgocadx: FTBFS in sid

[Gianfranco Costamagna]

Source: ginkgocadx
Version: 3.8.8-4
Severity: serious

Hello, looks like the current version in sid now FTBFS against new libdcmtk15

can you please have a look?
https://buildd.debian.org/status/fetch.php?pkg=ginkgocadx&arch=amd64&ver=3.8.8-4%2Bb1&stamp=1605242581&raw=0

A snip of the failing log is here:

cd /<>/obj-x86_64-linux-gnu/cadxcore && /usr/bin/c++ -DAPIEXPORT 
-DCURL_STATICLIB -DDCMTK_POST_20170228 -DGINKGO_ARCH_x86_64 
-DGINKGO_CODENAME=\"\" -DGINKGO_VERSION=\"3.8.8\" -DHAVE_CONFIG_H 
-DINTERNET_DIST -DITK_IO_FACTORY_REGISTER_MANAGER -DLINUX -DMONOLITIC 
-DUSE_SYSTEM_SQLITE -DUSING_EXTENSIONS -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 
-D__WXGTK__ -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 -DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpenGL)" 
-I/<>/obj-x86_64-linux-gnu/cadxcore/ITKFactoryRegistration 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gio-unix-2.0 -I/usr/include/pango-1.0 -I/usr/include/fribidi 
-I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libmount -I/usr/include/blkid 
-I/<>/cadxcore/CADxCore -I/<>/cadxcore 
-I/<>/cadxcore/vtk -I/<>/cadxcore/itk 
-I/<>/cadxcore/wx -I/<>/cadxcore/wx/VTK 
-I/<>/cadxcore/VTKInria3D 
-I/<>/cadxcore/VTKInria3D/wxVTK -I/usr/include/jsoncpp 
-I/<>/../lib/Linux-x86_64/libcurl-7.28.1/include 
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0 
-I/usr/include/vtk-6.3 -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/hdf5/openmpi 
-I/usr/include/libxml2 -isystem /usr/include/gdcm-3.0 -isystem 
/usr/include/ITK-4.13 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fPIC   -o 
CMakeFiles/CADxCore.dir/main/controllers/modalitysettingscontroller.cpp.o -c 
/<>/cadxcore/main/controllers/modalitysettingscontroller.cpp
[ 31%] Building CXX object 
cadxcore/CMakeFiles/CADxCore.dir/main/controllers/pacscontroller.cpp.o
cd /<>/obj-x86_64-linux-gnu/cadxcore && /usr/bin/c++ -DAPIEXPORT 
-DCURL_STATICLIB -DDCMTK_POST_20170228 -DGINKGO_ARCH_x86_64 
-DGINKGO_CODENAME=\"\" -DGINKGO_VERSION=\"3.8.8\" -DHAVE_CONFIG_H 
-DINTERNET_DIST -DITK_IO_FACTORY_REGISTER_MANAGER -DLINUX -DMONOLITIC 
-DUSE_SYSTEM_SQLITE -DUSING_EXTENSIONS -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 
-D__WXGTK__ -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 -DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpenGL)" 
-I/<>/obj-x86_64-linux-gnu/cadxcore/ITKFactoryRegistration 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gio-unix-2.0 -I/usr/include/pango-1.0 -I/usr/include/fribidi 
-I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libmount -I/usr/include/blkid 
-I/<>/cadxcore/CADxCore -I/<>/cadxcore 
-I/<>/cadxcore/vtk -I/<>/cadxcore/itk 
-I/<>/cadxcore/wx -I/<>/cadxcore/wx/VTK 
-I/<>/cadxcore/VTKInria3D 
-I/<>/cadxcore/VTKInria3D/wxVTK -I/usr/include/jsoncpp 
-I/<>/../lib/Linux-x86_64/libcurl-7.28.1/include 
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0 
-I/usr/include/vtk-6.3 -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/hdf5/openmpi 
-I/usr/include/libxml2 -isystem /usr/include/gdcm-3.0 -isystem 
/usr/include/ITK-4.13 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fPIC   -o 
CMakeFiles/CADxCore.dir/main/controllers/pacscontroller.cpp.o -c 
/<>/cadxcore/main/controllers/pacscontroller.cpp
In file included from 
/<>/cadxcore/main/controllers/dcmtk/libi2d/document2dcm.h:28,
 from 
/<>/cadxcore/main/controllers/dcmtk/dicomimg2dcm.h:29,
 from 
/<>/cadxcore/main/controllers/pacscontroller.cpp:22:
/<>/cadxcore/main/controllers/dcmtk/libi2d/d2dcommon.h:40

Processed: Re: Bug#974649: release.debian.org: new libnifti2 broke runtime (see #968730)

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 968730
Bug #974649 [release.debian.org] release.debian.org: new libnifti2 broke 
runtime (see #968730)
974649 was not blocked by any bugs.
974649 was not blocking any bugs.
Added blocking bug(s) of 974649: 968730
> tags -1 + moreinfo
Bug #974649 [release.debian.org] release.debian.org: new libnifti2 broke 
runtime (see #968730)
Added tag(s) moreinfo.

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

Processed: bug 974619 is forwarded to https://github.com/systemd/systemd/issues/17591

[Debian Bug Tracking System]

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

> forwarded 974619 https://github.com/systemd/systemd/issues/17591
Bug #974619 [src:systemd] FTBFS on mips*el: ../src/basic/macro.h:415:9: error: 
static assertion failed: "__NR_close_range == systemd_NR_close_range"
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/17591'.
> thanks
Stopping processing here.

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

Processed: new upstream 2.4.2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #973195 [src:python-asyncssh] python-asyncssh: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p "3.9 3.8" --system=custom 
"--test-args={interpreter} -m unittest discover -v" returned exit code 13
Added tag(s) patch.

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

Bug#973195: new upstream 2.4.2

[Matthias Klose]

Control: tags -1 + patch

the new upstream 2.4.2 fixes the 3.9 issues, and the package also seems to work
with python3-pycryptodome

one test is failing with both 3.8 and 3.9:

==
ERROR: test_confirm (tests.test_agent._TestAgent)
Test confirmation of key
--
Traceback (most recent call last):
  File "/<>/tests/util.py", line 69, in async_wrapper
return self.loop.run_until_complete(coro(self, *args, **kwargs))
  File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in 
run_until_complete
return future.result()
  File "/<>/tests/test_agent.py", line 52, in agent_wrapper
await func(self, agent)
  File "/<>/tests/test_agent.py", line 379, in test_confirm
sig = await agent_key.sign(b'test')
  File "/<>/asyncssh/agent.py", line 147, in sign
return await self._agent.sign(self.public_data, data, self._flags)
  File "/<>/asyncssh/agent.py", line 271, in sign
raise ValueError('Unable to sign with requested key')
ValueError: Unable to sign with requested key

--

packaging proposal at
https://launchpad.net/ubuntu/+source/python-asyncssh/2.4.2-0ubuntu1

Processed: severity of 974571 is important

[Debian Bug Tracking System]

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

> severity 974571 important
Bug #974571 [libx11-6] libx11-6: the locale is not supported by Xlib, 
continuing without locale support
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#974571: libx11-6: the locale is not supported by Xlib, continuing without locale support

[Tobias Frost]

Severity: -1 important

That's not a grave bug.

Bug#974563: corosync unable to communicate with pacemaker 1.1.16-1+deb9u1 which contains the fix for CVE-2020-25654

[Louis Sautier]

On 13/11/2020 12:23, Alejandro Taboada wrote:
> Maybe Corocync is not using peer communication? Could you check someway the 
> packet source address .. if it’s form localhost just allow, other check 
> permissions
> I know is not ideal but will solve a tot of production issues in the 
> meanwhile.
> 
> 
>> On 12 Nov 2020, at 23:20, Alejandro Taboada  
>> wrote:
>>
>> 
> 
> 
I'm not sure I understand what we need to look for.

Aren't they communicating via UNIX sockets from abstract namespaces
(@cib_rw@, @attrd@, etc.) ? That's what I see when I strace calls to
"crm resource cleanup " which also fails with the patched version.



signature.asc
Description: OpenPGP digital signature

Processed: found 972155 in 5.2.2.2-1~exp1, tagging 966594, tagging 964873

[Debian Bug Tracking System]

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

> found 972155 5.2.2.2-1~exp1
Bug #972155 {Done: Dmitry Shachnev } [src:dtkwidget] 
dtkwidget: FTBFS with Qt 5.15: error: aggregate 'QPainterPath borderPath' has 
incomplete type and cannot be defined
Marked as found in versions dtkwidget/5.2.2.2-1~exp1 and reopened.
> tags 966594 + sid bullseye
Bug #966594 [src:rt-app] rt-app: patch for newer json-c
Added tag(s) sid and bullseye.
> tags 964873 + sid bullseye
Bug #964873 [src:consul] consul: FTBFS: 
src/github.com/hashicorp/consul/agent/consul/server.go:467:29: cannot use 
s.logger (type *log.Logger) as type hclog.Logger in assignment
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Bug#974545: marked as done (fraqtive FTBFS: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined)

[Debian Bug Tracking System]

Your message dated Fri, 13 Nov 2020 11:33:33 +
with message-id 
and subject line Bug#974545: fixed in fraqtive 0.4.8-12
has caused the Debian Bug report #974545,
regarding fraqtive FTBFS: error: aggregate ‘QPainterPath path’ has incomplete 
type and cannot be defined
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.)


-- 
974545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fraqtive
Version: 0.4.8-11
Severity: serious
Tags: ftbfs

fraqtive fails to build from source in unstable:

| g++ -c -pipe -g -Wall -Wextra -D_REENTRANT -fPIC -DHAVE_SSE2 -DQT_OPENGL_LIB 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. -I. 
-I/usr/include/x86_64-linux-gnu/qt5 
-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/usr/include/x86_64-linux-gnu/qt5/QtXml 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I../tmp -I../tmp 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
../tmp/debug/configurationdata.o configurationdata.cpp
| configurationdata.cpp: In member function ‘bool 
ConfigurationData::checkAccess(const QString&)’:
| configurationdata.cpp:183:70: warning: ‘QStringList QString::split(QChar, 
QString::SplitBehavior, Qt::CaseSensitivity) const’ is deprecated: Use 
Qt::SplitBehavior variant instead [-Wdeprecated-declarations]
|   183 | QStringList pathParts = path.split( '/', QString::SkipEmptyParts 
);
|   |  ^
| In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qhashfunctions.h:44,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:47,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:45,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QVariant:1,
|  from configurationdata.h:22,
|  from configurationdata.cpp:19:
| /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:610:17: note: declared here
|   610 | QStringList split(QChar sep, SplitBehavior behavior,
|   | ^
| g++ -c -pipe -g -Wall -Wextra -D_REENTRANT -fPIC -DHAVE_SSE2 -DQT_OPENGL_LIB 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. -I. 
-I/usr/include/x86_64-linux-gnu/qt5 
-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/usr/include/x86_64-linux-gnu/qt5/QtXml 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I../tmp -I../tmp 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
../tmp/debug/datafunctions.o datafunctions.cpp
| datafunctions.cpp: In function ‘QPolygonF 
DataFunctions::interpolateCubic(const QPolygonF&)’:
| datafunctions.cpp:128:26: error: aggregate ‘QPainterPath path’ has incomplete 
type and cannot be defined
|   128 | QPainterPath path;
|   |  ^~~~
| make[2]: *** [Makefile:1161: ../tmp/debug/datafunctions.o] Error 1
| make[2]: Leaving directory '/<>/src'
| make[1]: *** [Makefile:47: sub-src-make_first] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:16: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

This seems to be recent and caused by some other package being updated.

Helmut
--- End Message ---
--- Begin Message ---
Source: fraqtive
Source-Version: 0.4.8-12
Done: =?utf-8?q?Patrick_Matth=C3=A4i?= 

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

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated fraqtive 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: Fri, 13 Nov 2020 11:38:15 +0100
Source: fraqtive
Architecture: source
Version: 0.4.8-12
Distribution: unstable
Urgency: medium
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Closes: 974545
Changes:
 fraqtive (0.4.8-12) u

Bug#974563: corosync unable to communicate with pacemaker 1.1.16-1+deb9u1 which contains the fix for CVE-2020-25654

[Alejandro Taboada]

Maybe Corocync is not using peer communication? Could you check someway the 
packet source address .. if it’s form localhost just allow, other check 
permissions
I know is not ideal but will solve a tot of production issues in the meanwhile.


> On 12 Nov 2020, at 23:20, Alejandro Taboada  
> wrote:
> 
> 

Bug#973889: marked as done (raptor2: CVE-2017-18926)

[Debian Bug Tracking System]

Your message dated Fri, 13 Nov 2020 11:03:33 +
with message-id 
and subject line Bug#973889: fixed in raptor2 2.0.14-1.1~deb10u1
has caused the Debian Bug report #973889,
regarding raptor2: CVE-2017-18926
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.)


-- 
973889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: raptor2
Version: 2.0.14-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 raptor2.

CVE-2017-18926[0]:
| raptor_xml_writer_start_element_common in raptor_xml_writer.c in
| Raptor RDF Syntax Library 2.0.15 miscalculates the maximum nspace
| declarations for the XML writer, leading to heap-based buffer
| overflows (sometimes seen in raptor_qname_format_as_xml).


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-2017-18926
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18926
[1] 
https://github.com/LibreOffice/core/blob/master/external/redland/raptor/0001-Calcualte-max-nspace-declarations-correctly-for-XML-.patch.1
[2] https://www.openwall.com/lists/oss-security/2017/06/07/1

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: raptor2
Source-Version: 2.0.14-1.1~deb10u1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated raptor2 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: Fri, 06 Nov 2020 22:46:38 +0100
Source: raptor2
Architecture: source
Version: 2.0.14-1.1~deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Dave Beckett 
Changed-By: Salvatore Bonaccorso 
Closes: 973889
Changes:
 raptor2 (2.0.14-1.1~deb10u1) buster-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Rebuild for buster-security
 .
 raptor2 (2.0.14-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Calcualte max nspace declarations correctly for XML writer
 (CVE-2017-18926) (Closes: #973889)
Checksums-Sha1: 
 7054748d4f99239718a90fad48f571abb627afd6 2308 raptor2_2.0.14-1.1~deb10u1.dsc
 f0dc155ee616aac0e5397dd659519c9d0a262f21 1877454 raptor2_2.0.14.orig.tar.gz
 55bc009e40ed5fe27320245a89ae9e4ee6658a46 8372 
raptor2_2.0.14-1.1~deb10u1.debian.tar.xz
Checksums-Sha256: 
 b9d9c09236ac0580c9a1404d61f867fae5519b330c68a0c271a699eb65443153 2308 
raptor2_2.0.14-1.1~deb10u1.dsc
 cb447b7c684cbe60f1266d622691fd20fdcf7b91f4a470c6de5fc8e8961df1b2 1877454 
raptor2_2.0.14.orig.tar.gz
 b70ff4ad71f3e440eb7268d2bdcef6d6ae16b2b35990d9937b5bfb622f0fbd17 8372 
raptor2_2.0.14-1.1~deb10u1.debian.tar.xz
Files: 
 f6da6287ef6fdcc374689f5a0e0f470e 2308 devel optional 
raptor2_2.0.14-1.1~deb10u1.dsc
 d3e0b43866197a5367b781b25510f728 1877454 devel optional 
raptor2_2.0.14.orig.tar.gz
 eb064a4d4035760e6330dc283a56ab74 8372 devel optional 
raptor2_2.0.14-1.1~deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl+lxWdfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EebYP/AhVwSHsI8mugL1Wf+rHV0Z/KwKN634U
pqV6EeeYrp+KVEAIPZOvYE4rpD4egw+iCLyZLtkgJHkjNCUpzNnz8WNH//bVjT8k
QSBq8vj2vlyS8f/uron3sikIkvD7tRszAxuqcNIgrmOcGMoKhchVl6koY0wHSK2K
rwXo+5tsvnyrqfEQV35PxjFpSCdUv/utfZ8shIO40n9d5XuE1o3B5GbxHqcAkHTp
xjm5iYzHNZ8yxikNrRluq2s0BVeb6SrnnBMF+6U9e4yJ2eDDMghahNjxDA5t/FO8
067Of6rY/+ePXZYbvUwX9NlBtOfCqC3eRhxFJWOae+i+dWSE95ZjLP/Sf7cES0j3
f0NpT1M9wTkiw1K+o326OYL/25GYxKJxWHkSBIKWEza7dE9YdzXCLVRPHby1uhMt
9LUqVD9Sp7ThOLRkjr9EDJQjlsh+GOe1gNcLJLLcX1q8qqP386s3egMNvS/IQk8Y
YRkZG2jqxZsAGCSgYJ/GhbHZeGbkuaq9qP4feZW/pBBdLGW0nOgXgRZDV2lPYKs5
tLZZIBXu7X7E5qQu/gwSIdGXoLp6O

Bug#973748: marked as done (sddm: CVE-2020-28049: local privilege escalation due to race condition in creation of the Xauthority file)

[Debian Bug Tracking System]

Your message dated Fri, 13 Nov 2020 11:03:37 +
with message-id 
and subject line Bug#973748: fixed in sddm 0.18.0-1+deb10u1
has caused the Debian Bug report #973748,
regarding sddm: CVE-2020-28049: local privilege escalation due to race 
condition in creation of the Xauthority file
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.)


-- 
973748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sddm
Version: 0.18.1-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 sddm.

CVE-2020-28049[0]:
| local privilege escalation due to race condition in creation of the
| Xauthority file

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-28049
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28049
[1] https://github.com/sddm/sddm/commit/be202f533ab98a684c6a007e8d5b4357846bc222
[2] https://bugzilla.suse.com/show_bug.cgi?id=1177201
[3] https://www.openwall.com/lists/oss-security/2020/11/04/2

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: sddm
Source-Version: 0.18.0-1+deb10u1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated sddm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Nov 2020 15:29:27 +0100
Source: sddm
Architecture: source
Version: 0.18.0-1+deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Salvatore Bonaccorso 
Closes: 973748
Changes:
 sddm (0.18.0-1+deb10u1) buster-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fix X not having access control on startup (CVE-2020-28049)
 (Closes: #973748)
Checksums-Sha1: 
 6a6813f739dd6f78a3b4b358d85ca64ba5d57d33 2834 sddm_0.18.0-1+deb10u1.dsc
 d6b5dc3ec560acdfa3afb6e7a88d062b45378930 3526688 sddm_0.18.0.orig.tar.gz
 d7b2b8a20ec040be316fedb2f213249a339f1a2f 52856 
sddm_0.18.0-1+deb10u1.debian.tar.xz
Checksums-Sha256: 
 4257601035f4a2c0a50afaf120e7d4fd1418aac2ef6b44d9497c52eab3a6eeec 2834 
sddm_0.18.0-1+deb10u1.dsc
 9c50b6194f1b4dbf6e1a1b21f23c2c5e384871172985e192b91585986d38eec4 3526688 
sddm_0.18.0.orig.tar.gz
 6e3a85f8af20d9b5f6a5b91ed2552f680ff964e6ba85ced3eb5659bee7522a54 52856 
sddm_0.18.0-1+deb10u1.debian.tar.xz
Files: 
 17bef940125e17671ee5b7abd44be783 2834 kde optional sddm_0.18.0-1+deb10u1.dsc
 f8656aa61020c727b6925225fa681996 3526688 kde optional sddm_0.18.0.orig.tar.gz
 bd8ea261aacb78364696f0dfafd7d643 52856 kde optional 
sddm_0.18.0-1+deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl+ivGxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E/qIP/RkmzS3V14XpjILPGJYs0fFqvii6l6AZ
d8I6u/KUdn4Q+6nZ5YGDLvNTqC8Q5/TcaaNSoJ3drxBB2lretIISLPGsweeNDPpk
ldccd97uvEUTRQAhquWppqJUbYaiYkTPvUeMArYGOuKnkimOGJXTgJ8ZWH05ziSb
xpXQmDHzkTren8OONCasvk5d83RKo7J6UelS/fhPIDPOb0wtBgbx3DIWvLNIMW/k
vTSUFf9VjAwas93AEIpBPoT3qkPt8gda3JBaMx7lptAia8FNO/7XT+oKHEjrKowS
8slTDM/noNjpankoicUBNAoBpsh5Fv6/Y8uVf8DyYx4mVFzzRDB7R3s4eZLEukDj
I5PpG8f2lavp3/OjCxs27pJ4pdUA3ZjKcpDDH99qp0V5DAzMBE+5/0CdPbxxY8Hb
Xmm/RR0/OwguRIwuUNytoTDJzUUJ4ZTwB2lkfOewnpaRaQNCuplh4AlMojRug2zV
YKc2mq6cCktVYUNLhiuWTsgBlAIFs37eatRnHBMhfO6k9Sfa7c9KJEAeTYnkjGrz
+YJR1/h1UPczsQYfcFnnZK5JGG483f095/NgruDhEKNKPKTLxJrulAkOv0Vy+Tz7
eJ/CBz6UgeMVaaJFMwNuFR8UFcW3UEZ4si1VqhwhIpzxY3wbXFovHNatsqsqvmrY
oSsdDiaEXnqi
=cFtB
-END PGP SIGNATURE End Message ---

Bug#974639: [Pkg-rust-maintainers] Bug#974639: Bug#974639: rust-zoxide: wrong section in debian/control

[Sylvestre Ledru]

Le 13/11/2020 à 11:45, Adrian Bunk a écrit :

On Fri, Nov 13, 2020 at 09:02:52AM +0100, Sylvestre Ledru wrote:

Le 13/11/2020 à 08:44, Aurelien Jarno a écrit :

Source: rust-zoxide
Version: 0.4.3-1
Severity: serious

Could the rust tooling create "Section: fixme" instead?
This would give you the lintian warning while not
causing problems if accidentally uploaded.


Yeah, I already pushed a fix for that
https://salsa.debian.org/rust-team/debcargo/-/commit/de1c4c95a9a7488f3d076f7397843f32b09c3395


Cheers,
S

Bug#973167: ufonormalizer: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

[Matthias Klose]

Control: forwarded -1 
https://github.com/unified-font-object/ufoNormalizer/issues/73

deprecated features in Python 3.4 ...

there's a proposal to re-introduce the deprecated Data class to work around it.

Processed: Re: ufonormalizer: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/unified-font-object/ufoNormalizer/issues/73
Bug #973167 [src:ufonormalizer] ufonormalizer: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13
Set Bug forwarded-to-address to 
'https://github.com/unified-font-object/ufoNormalizer/issues/73'.

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

Bug#974639: [Pkg-rust-maintainers] Bug#974639: rust-zoxide: wrong section in debian/control

[Adrian Bunk]

On Fri, Nov 13, 2020 at 09:02:52AM +0100, Sylvestre Ledru wrote:
> Le 13/11/2020 à 08:44, Aurelien Jarno a écrit :
> > Source: rust-zoxide
> > Version: 0.4.3-1
> > Severity: serious
> > 
> > rust-zoxide contains an invalid Section for the Source package:
> > 
> > | Source: rust-zoxide
> > | Section: FIXME-(source.section)
> > | Priority: optional
> > | Build-Depends: debhelper (>= 11),
> > |  dh-cargo (>= 18),
> > |  cargo:native,
> > |  rustc:native,
> > |  libstd-rust-dev,
> > |  librust-anyhow-1+default-dev (>= 1.0.28-~~),
> > |  librust-bincode-1+default-dev (>= 1.3.1-~~),
> > 
> > This causes many issues with the debian tools (buildds, etc.)
> 
> Lintian only shows a warning. Should it become an error ?
> W: zoxide: unknown-section FIXME-(source.section)

Sections in the archive are set by the overrides,
so having incorrect information there is mostly irrelevant.
And the ftp team just moved 1k packages into a new golang section 
lintian might not yet know about.

An unrelated question is why the lintian warning was missed before 
uploading.

> Or it is the parenthesis?
> ...

The syntax error broke uploading from the buildds,
this is the real problem.

Could the rust tooling create "Section: fixme" instead?
This would give you the lintian warning while not
causing problems if accidentally uploaded.

> Thanks
> S

cu
Adrian

Processed: Re: SO version specification changed upstream

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #968730 [libnifti2] libnifti2: libniftiio.so.2 not provided
Severity set to 'serious' from 'normal'

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

Processed: Re: Reopening for mips/s390x failures

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #968339 [src:kodi] kodi: FTBFS in sid (test failures)
Severity set to 'important' from 'serious'
> close -1
Bug #968339 [src:kodi] kodi: FTBFS in sid (test failures)
Marked Bug as done

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

Bug#968339: Reopening for mips/s390x failures

[Tobias Frost]

Control: severity -1 important
Control: close -1

On Wed, 09 Sep 2020 08:33:00 + Vasyl Gello  wrote:
> Control: reopen !
> 
> I am reopening this bug as mipsel test failures are caused by ld.gold usage
filed separately.

Those issue* seems not to be related to this bug, so I don't think reopening
this bug is right then. If you disagree, please expand why reopening this bug.

Regardless, as kodi has never been compiled for mips, this bug is not RC,
so I will reduce its severity for now and then close it.

Feel free to reopen with your expansion.

*I guess you are referring to #969946.


-- 
tobi (who was wondering why kodi is not in testing)

Bug#973193: parso: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13

[Matthias Klose]

Control: tags -1 + patch

fixed by new upstream 0.8
example packaging (no changes) at
https://launchpad.net/ubuntu/+source/parso/0.8.0-0ubuntu1

Bug#973660: marked as done (thunderbird: FTBFS on s390x in buster)

[Debian Bug Tracking System]

Your message dated Fri, 13 Nov 2020 10:17:08 +
with message-id 
and subject line Bug#973660: fixed in thunderbird 1:78.4.2-1~deb10u1
has caused the Debian Bug report #973660,
regarding thunderbird: FTBFS on s390x in buster
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.)


-- 
973660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:thunderbird
Version: 78.3.1-2~deb10u1
Severity: serious
Tags: ftbfs
Control: affects -1 release.debian.org security.debian.org
X-Debbugs-Cc: t...@security.debian.org

Hi,

Since 78.3.1, thunderbird FTBFS on s390x in buster(-security).

The relevant part of the logs appears to be:

make[5]: Entering directory 
'/<>/obj-thunderbird/config/external/icu/data'
mkdir -p '.deps/'
config/external/icu/data/icudata_gas.o
/usr/bin/clang -std=gnu99 -o icudata_gas.o -DNDEBUG=1 -DTRIMMED=1 -fPIC 
-Wa,--noexecstack -include /<>/obj-thunderbird/mozilla-config.h 
-DMOZILLA_CLIENT -g -I/<>/config/external/icu/data 
-I/<>/config/external/icu/data/ '-DICU_DATA_FILE="icudt67b.dat"' 
-DICU_DATA_SYMBOL=icudt67_dat  -c 
/<>/config/external/icu/data/icudata_gas.S
/<>/config/external/icu/data/icudata_gas.S:17:17: error: Could not 
find incbin file 'icudt67b.dat'
.incbin "icudt67b.dat"
^
make[5]: *** [/<>/config/rules.mk:743: icudata_gas.o] Error 1
make[5]: Leaving directory 
'/<>/obj-thunderbird/config/external/icu/data'
make[4]: *** [/<>/config/recurse.mk:74: 
config/external/icu/data/target-objects] Error 2

Regards,

Adam
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:78.4.2-1~deb10u1
Done: Carsten Schoenert 

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
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, 11 Nov 2020 20:06:07 +0100
Source: thunderbird
Architecture: source
Version: 1:78.4.2-1~deb10u1
Distribution: stable-security
Urgency: medium
Maintainer: Carsten Schoenert 
Changed-By: Carsten Schoenert 
Closes: 973660
Changes:
 thunderbird (1:78.4.2-1~deb10u1) stable-security; urgency=medium
 .
   * Rebuild for buster-security
(Closes: #973660)
   [ Emilio Pozuelo Monfort ]
   * [3d58cc1] d/control: reenable the armhf build on buster
Checksums-Sha1:
 c2aa0aabdf614683674ae3d289f131dd2a280b48 12084 thunderbird_78.4.2-1~deb10u1.dsc
 76a73c06ddf188bf7dea175cd521e45d17c66c7f 11808976 
thunderbird_78.4.2.orig-thunderbird-l10n.tar.xz
 ea0551fa9e21205c4808255d185772bc3211f41a 372974244 
thunderbird_78.4.2.orig.tar.xz
 f35706b1b4602353e65bdcc4d1d63d1b1bb712c1 825624 
thunderbird_78.4.2-1~deb10u1.debian.tar.xz
Checksums-Sha256:
 e566a865088b5a51486463fa68cff34c94c4362510b0cd88f1740a6b110848d1 12084 
thunderbird_78.4.2-1~deb10u1.dsc
 0a63a1d84c7c5ffd1c5a992af46c0259776d29b97e42657298a04f33865c6e29 11808976 
thunderbird_78.4.2.orig-thunderbird-l10n.tar.xz
 9978c15684a701e839aa286f2f438e69efd7f9396e740f9de8c10a7dec8bfced 372974244 
thunderbird_78.4.2.orig.tar.xz
 48e66e4d3461b9e1f8c66e30b5ec156fda8a6e1432f6d9b512c9a24c23ad53c9 825624 
thunderbird_78.4.2-1~deb10u1.debian.tar.xz
Files:
 862c7c266e4c24ce0b661456b725970a 12084 mail optional 
thunderbird_78.4.2-1~deb10u1.dsc
 dbb0b2aec04855379ca425348e41c782 11808976 mail optional 
thunderbird_78.4.2.orig-thunderbird-l10n.tar.xz
 06adea8bcc43e400ee06e6ecd2e6a326 372974244 mail optional 
thunderbird_78.4.2.orig.tar.xz
 6db79e070db9f564dd7431e8d93b7500 825624 mail optional 
thunderbird_78.4.2-1~deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAl+teMcACgkQgwFgFCUd
HbDeuxAAgFLW+Oj1GIveeWwkGnt0+fyBw47SFbm++7ig2Qy3dFqKsTKGzqtf/JKH
4o89cLExw8au4NQX7/NT7YiYtwclgUl0O7POai4BjZiAVmFRBPLn8gG4UQw/sntM
s5srskyW2SQQn02hGAiXkUyguwWtX9Coyp/DPWpzU3TujhArlekZCMPvG40ww2H1
g/Z6zaSTjQ3ac5EI5ybCMz1oODIyaEBGWcHdSmEVaNBCB9+6+K1SEyScASbxDcxu
VS067luPulhOq7zE5gL9AzZeKuUTh40jcYuDsQaxcmXZFHf0a8Zi2RzUAsGGW40L
M0keup/

Processed: Re: parso: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #973193 [src:parso] parso: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
Added tag(s) patch.

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

Bug#973114: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13

[Matthias Klose]

Control: tags -1 + patch

patch at
http://launchpadlibrarian.net/506790173/python-future_0.18.2-4_0.18.2-4ubuntu1.diff.gz

Processed: Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #973114 [src:python-future] python-future: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 
13
Added tag(s) patch.

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

Bug#973121: cairocffi: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

[Matthias Klose]

Control: tags -1 + patch

fixed in new upstream version 1.2.0.

example packaging at
https://launchpad.net/ubuntu/+source/cairocffi/1.2.0-0ubuntu3

this disables the flake8 tests, and the isort tests, pytest-isort is not yet
packaged for Debian.

Processed: Re: cairocffi: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #973121 [src:cairocffi] cairocffi: FTBFS: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.9 3.8" returned exit code 13
Added tag(s) patch.

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

Bug#973126: responses: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13

[Matthias Klose]

new upstream 0.12. 0.11 is said to support 3.9, 0.10 is said to support 3.8

Bug#974639: marked as done (rust-zoxide: wrong section in debian/control)

[Debian Bug Tracking System]

Your message dated Fri, 13 Nov 2020 08:44:54 +
with message-id 
and subject line Bug#974639: fixed in rust-zoxide 0.4.3-2
has caused the Debian Bug report #974639,
regarding rust-zoxide: wrong section in debian/control
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.)


-- 
974639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-zoxide
Version: 0.4.3-1
Severity: serious

rust-zoxide contains an invalid Section for the Source package:

| Source: rust-zoxide
| Section: FIXME-(source.section)
| Priority: optional
| Build-Depends: debhelper (>= 11),
|  dh-cargo (>= 18),
|  cargo:native,
|  rustc:native,
|  libstd-rust-dev,
|  librust-anyhow-1+default-dev (>= 1.0.28-~~),
|  librust-bincode-1+default-dev (>= 1.3.1-~~),

This causes many issues with the debian tools (buildds, etc.)
--- End Message ---
--- Begin Message ---
Source: rust-zoxide
Source-Version: 0.4.3-2
Done: Sylvestre Ledru 

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated rust-zoxide 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: Fri, 13 Nov 2020 09:14:05 +0100
Source: rust-zoxide
Architecture: source
Version: 0.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Sylvestre Ledru 
Closes: 974639
Changes:
 rust-zoxide (0.4.3-2) unstable; urgency=medium
 .
   * Package zoxide 0.4.3 from crates.io using debcargo 2.4.3
   * Fix the section (Closes: #974639)
   * Add a manpage
Checksums-Sha1:
 7e298a93c60eea694a418b5e82127f3a496d9f2a 2448 rust-zoxide_0.4.3-2.dsc
 2728bdc8581e7d8b97a43fd5ba68830fb81e77da 2840 rust-zoxide_0.4.3-2.debian.tar.xz
 9e2a42eece53ba9b25f8d0af84da1de04c29f568 9604 
rust-zoxide_0.4.3-2_source.buildinfo
Checksums-Sha256:
 855760499cfc352c2a78a61ca9cc724a5ff7e24cd8c97f6cb85a6b4195dcd80b 2448 
rust-zoxide_0.4.3-2.dsc
 4e141bd3c7426f02410008d86e35f7f2cff593547cfa747b6a7040e09bdd08cd 2840 
rust-zoxide_0.4.3-2.debian.tar.xz
 cb66771a578721b1d991f927851b70b833475a6c8a4b7f560b3f3a05e5726a06 9604 
rust-zoxide_0.4.3-2_source.buildinfo
Files:
 ea50cde176991960826502437ac5ac07 2448 utils optional rust-zoxide_0.4.3-2.dsc
 12be165817f931b6e9fba48dbf2782b8 2840 utils optional 
rust-zoxide_0.4.3-2.debian.tar.xz
 eb821d91a96ef9695c86c047c5e52732 9604 utils optional 
rust-zoxide_0.4.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAl+uQFAACgkQfmUo2nUv
G+EgFQ/8CJnHL8LQ9KLIq+H3m2sT7pXKESOlHHfqPjqt5Nxt5z7/q0Q0GT88QjQI
jHh3gvEWQo95JHJkepjGnbxEufbtzcvQyVq3StbryWpXCtNkAgXN0LJxFxtislAs
acTXSsxAxXAzFv6MyWy7J1XiLtc/ABsYzr1WfTa3RHAUKzBI7vaFRsYVADGlvRoz
RUNWjhui3HLzkkXbUFRf5qRgvz6uwwG7lnMhgYHGHql8n17jje/6mHQE76GJzA1L
uF8sn5N7LQZFHLHqtF5syN7+QhIaegkrfAuLVXzUvy+OWIDZWPEQWcExdN/6uo7d
6pI8G1pfZHxMiMXQ9Vk5qz93rvBo4fzuEtOwjeKcKRhnXZ7WyxBb3cETGxj80aye
JH7ITNTLZcr32D8VwIgjdEYpisX4Ur/+dBcC2+It6zFJnClR9l9JxNa6lhRNqFBE
Vk0KqywDFGRpaI0K1B85oAYEmgnfEHEo7jQOXtiwF3MOvjdpSXC+yuRfQ5xpvOxH
U7pqKhRYFPwDkBai6SN4zghSHv2iUJHiUrW/0+fggiHOFSgFKfiwcfTTOXJWFDZf
uWT+sB5S80zyBmvYWApEvg/xTY17buqLFCOzolpjxwFrlA5dAlyhzL+MtY+QFNDP
3gyvC1+NH7z+5pjlWYtGYHehJ1h+PbAGGUD4kQvjc0KvqFCdvRA=
=rXL0
-END PGP SIGNATURE End Message ---

Processed: Re: python-webob: FTBFS: tests failed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #973134 [src:python-webob] python-webob: FTBFS: tests failed
Added tag(s) patch.

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

Bug#973134: python-webob: FTBFS: tests failed

[Matthias Klose]

Control: tags -1 + patch

fixed by upstream pull request 411, uploaded to the delayed queue

Bug#974637: [Debian-med-packaging] Bug#974637: biosig4c++_1.9.5-1+b2_mipsel-buildd.changes REJECTED

[Graham Inggs]

Hi

On Fri, 13 Nov 2020 at 09:45, Aurelien Jarno  wrote:
> Version check failed:
> Your upload included the binary package biosig-tools, version 1.9.5-1+b2, for 
> mipsel,
> however testing already has version 2.0.6-1+b1.
> Uploads to unstable must have a higher version than present in testing.

It seems src:biosig4c++'s binaries have been taken over by src:biosig.
The biosig4c++ package needs to be removed from unstable.

Regards
Graham

Bug#974639: [Pkg-rust-maintainers] Bug#974639: rust-zoxide: wrong section in debian/control

[Sylvestre Ledru]

Le 13/11/2020 à 08:44, Aurelien Jarno a écrit :

Source: rust-zoxide
Version: 0.4.3-1
Severity: serious

rust-zoxide contains an invalid Section for the Source package:

| Source: rust-zoxide
| Section: FIXME-(source.section)
| Priority: optional
| Build-Depends: debhelper (>= 11),
|  dh-cargo (>= 18),
|  cargo:native,
|  rustc:native,
|  libstd-rust-dev,
|  librust-anyhow-1+default-dev (>= 1.0.28-~~),
|  librust-bincode-1+default-dev (>= 1.3.1-~~),

This causes many issues with the debian tools (buildds, etc.)


Lintian only shows a warning. Should it become an error ?
W: zoxide: unknown-section FIXME-(source.section)

Or it is the parenthesis?
(I will fix it in a sec)


Thanks
S