Processed: python2.7 removal in bookworm

[Debian Bug Tracking System]

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

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

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

Processed: notfound 1010901 in 42.1-3

[Debian Bug Tracking System]

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

> notfound 1010901 42.1-3
Bug #1010901 {Done: Paul Gevers } [gpaste] missing license 
information
There is no source info for the package 'gpaste' at version '42.1-3' with 
architecture ''
Unable to make a source version for version '42.1-3'
Ignoring request to alter found versions of bug #1010901 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Re: Processed: found in testing

[Debian Bug Tracking System]

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

> # turns out we made a mistake (discussion on #d-release)
> notfound 1010901 42.1-3
Bug #1010901 [gpaste] missing license information
There is no source info for the package 'gpaste' at version '42.1-3' with 
architecture ''
Unable to make a source version for version '42.1-3'
No longer marked as found in versions 42.1-3.
> fixed 1010901 42.1-2
Bug #1010901 [gpaste] missing license information
There is no source info for the package 'gpaste' at version '42.1-2' with 
architecture ''
Unable to make a source version for version '42.1-2'
Marked as fixed in versions 42.1-2.
> close 1010901
Bug #1010901 [gpaste] missing license information
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: found in testing

[Debian Bug Tracking System]

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

> found 1010901 42.1-3
Bug #1010901 {Done: Jérémy Lal } [gpaste] missing license 
information
There is no source info for the package 'gpaste' at version '42.1-3' with 
architecture ''
Unable to make a source version for version '42.1-3'
Marked as found in versions 42.1-3 and reopened.
> thanks
Stopping processing here.

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

Processed: tagging 1015925

[Debian Bug Tracking System]

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

> tags 1015925 + pending
Bug #1015925 [libcwidget-dev] libcwidget-dev: causes aptitude FTBFS due to 
missing #include 
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1015925: cwidget RC bug: Please upload or grant me cwidget team membership on Salsa

[Axel Beckert]

Hi Manuel,

Manuel A. Fernandez Montecelo wrote:
> > I know you're busy with RISC-V and other stuff, but please do me a
> > small favour and add me to the cwidget team on Salsa, probably via
> > https://salsa.debian.org/groups/cwidget-team/-/group_members
> 
> Yeah, I dedicate my stuff mostly to RISC-V because I have nothing to
> spare in the last few years, and even there I'm lacking :-(

Oh. :-/

> I had seen this from pabs but will not have time at least until mid
> next week, so better if you do it and have permissions in general
> anyway, as you say.

Thanks for adding my to the cwidget team. I will do an cwidget upload
within the next few days and afterwards an aptitude upload.

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

Processed: found 1010901 in 3.42.6-1

[Debian Bug Tracking System]

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

> # this bug also affects testing, maybe marking it properly helps migration
> found 1010901 3.42.6-1
Bug #1010901 {Done: Jérémy Lal } [gpaste] missing license 
information
Marked as found in versions gpaste/3.42.6-1.
> thanks
Stopping processing here.

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

Bug#1012895: cwidget RC bug: Please upload or grant me cwidget team membership on Salsa

[Manuel A. Fernandez Montecelo]

Hi,

On Thu, 4 Aug 2022 at 18:03, Axel Beckert  wrote:
>
> Hi Manuel,
>
> TL;DR: Please grant me cwidget team membership on Salsa so we don't
> have to NMU it. Or just do an upload of cwidget with the patch from
> #1015925.
>
> I know you're busy with RISC-V and other stuff, but please do me a
> small favour and add me to the cwidget team on Salsa, probably via
> https://salsa.debian.org/groups/cwidget-team/-/group_members

Yeah, I dedicate my stuff mostly to RISC-V because I have nothing to
spare in the last few years, and even there I'm lacking :-(

I had seen this from pabs but will not have time at least until mid
next week, so better if you do it and have permissions in general
anyway, as you say.

Thanks both of you, pabs and abe, for taking care!

-- 
Manuel A. Fernandez Montecelo 

Bug#1016670: libconfig-model-dpkg-perl: autopkgtest failures

[gregor herrmann]

Source: libconfig-model-dpkg-perl
Version: 2.162
Severity: serious
Justification: autopkgtest failures are serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

libconfig-model-dpkg-perl fails its autopkgtests both on ci.d.n and
locally. (But not the tests during build.)

https://ci.debian.net/data/autopkgtest/unstable/amd64/libc/libconfig-model-dpkg-perl/24124550/log.gz
and copied from a local test:

…
ok 106 - test debhelper migration
In config class 'Dpkg::Control::Source', (location: control source Vcs-Browser) 
element 'Vcs-Browser' (level normal) has a configuration model error:
Compute argument 'pkgname', error with '- Source':
Configuration item 'control source Source' has a wrong value:
Undefined mandatory value.
value is computed from 'use Cwd; my $res = getcwd =~ 
m!/([a-z0-9][a-z0-9+.-]+)$! ? $1 : undef;
'

# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 106.
Dubious, test returned 255 (wstat 65280, 0xff00)
All 106 subtests passed

2022/08/04 22:40:52 write backend Dpkg Config::Model::Backend::Dpkg::write 
failed: In config class 'Dpkg', (location: changelog) element 'changelog' 
(level normal) has a configuration model error:
Compute argument 'pkg_name', error with '! control source Source':
Configuration item 'control source Source' has a wrong value:
Undefined mandatory value.
value is computed from 'use Cwd; my $res = getcwd =~ 
m!/([a-z0-9][a-z0-9+.-]+)$! ? $1 : undef;
'
…
2022/08/04 22:40:53 write backend Dpkg::Control 
Config::Model::Backend::Dpkg::Control::write failed: Configuration item 
'control source Source' has a wrong value:
Undefined mandatory value.
value is computed from 'use Cwd; my $res = getcwd =~ 
m!/([a-z0-9][a-z0-9+.-]+)$! ? $1 : undef;
'
Configuration item 'control source Source' has a wrong value:
Undefined mandatory value.
value is computed from 'use Cwd; my $res = getcwd =~ 
m!/([a-z0-9][a-z0-9+.-]+)$! ? $1 : undef;
'
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 1.
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed
…
Test Summary Report
- ---
t/dependency-check.t(Wstat: 65280 Tests: 106 Failed: 0)
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
t/dpkg.t(Wstat: 65280 Tests: 1 Failed: 0)
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output


Cheers,
gregor


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

Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmLsTPZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZYGxAAinz/gSzn2nE8VI2sFIySHIp+S56WyiRKV23chG2dOQ3osq8WDQ9U5Oq1
inJd5xcOmKKmBcZ7weoC8IeLhCrIKPDzvp5/YzDPUkXSMehANBqzJi9baXbZjkUG
QTnRmoF4Os7+0PqU9Ji8bQtcWSAeW01SFYRGNWi2dmGAorPAewMSoQ2NF9G+a/4U
XtHjdQt2dJd0TFwdK1s/KeKHvE5sGqhLDBzoxb6R9nV7e5zMjDsNTxzG8vuv6qVz
qb0mviF+hKEZtKYloiotKY19sxh5ecqhx0GGuADl5jkTXB5Wv9nxSlU3f30oDqN+
Ynjyu78gLTnpWDPSpl58ShXCJRszUPhH3hc04yu3c/moxKn6L3oXkjZoKY/CBi2S
dDpFr/x+eXLDYhSFHsLROAm6mZ5CffnAfQYSKE8hQup5f4+9pnB4gxQbDewxsb+l
yjfewjTK6mZ3H9CMIX33d+Ai6LLrInr7vZNTIu8mf7YFaZC98mt8S/w/0g95s1/r
Ozl5vylt40oEEG4ZftwqW8+Wt1MJG5r2hS3klLzXD85DWiHKDfsT7EE+nEo7P8s7
6ChLhRv0nzYqG9NKwqpYnBxa1/q+ul0MNu5GXTHHUiB4FyxXbZ8jDQZtKwYrVpXp
AGoSG1+iChjCNSsPoR9KUxEN0VLH6udgKryRq5Nq+pVbyfEJn4Y=
=jaGK
-END PGP SIGNATURE-

Bug#1014884: marked as done (statsmodels: FTBFS on mipsel (pythran shifted tolerances))

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 22:21:58 +
with message-id 
and subject line Bug#1014884: fixed in statsmodels 0.13.2+dfsg-4
has caused the Debian Bug report #1014884,
regarding statsmodels: FTBFS on mipsel (pythran shifted tolerances)
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.)


-- 
1014884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: statsmodels
Version: 0.13.2+dfsg-2
Severity: serious
Justification: FTBFS
Control: forwarded -1 https://github.com/statsmodels/statsmodels/issues/8341

mipsel is failing to build statsmodels 0.13.2+dfsg-2.

Problem seems to be another shift in tolerance requirements triggered
by scipy using pythran, similar to Bug#1014278.

In this case the discrepancy is mild, gets error 1.12443388e-12,
but expects 1e-12. Could be worked around by relaxing the tolerance to 2e-12

The error message is

 TestGMMStOneiterOLS_Linear.test_basic _

self = 


def test_basic(self):
res1, res2 = self.res1, self.res2
# test both absolute and relative difference
rtol,  atol = self.params_tol
assert_allclose(res1.params, res2.params, rtol=rtol, atol=0)
>   assert_allclose(res1.params, res2.params, rtol=0, atol=atol)
E   AssertionError: 
E   Not equal to tolerance rtol=0, atol=1e-12
E   
E   Mismatched elements: 1 / 13 (7.69%)
E   Max absolute difference: 1.12443388e-12
E   Max relative difference: 1.53607078e-12
Ex: array([ 6.195478e-02,  2.712120e-03,  3.083947e-02,  4.216306e-02,
E  -9.629347e-02,  1.328993e-01, -5.420948e-02,  8.058085e-02,
E   2.075915e-01,  2.282237e-01,  2.226915e-01,  3.228747e-01,
E   4.235357e+00])
Ey: array([ 6.195478e-02,  2.712120e-03,  3.083947e-02,  4.216306e-02,
E  -9.629347e-02,  1.328993e-01, -5.420948e-02,  8.058085e-02,
E   2.075915e-01,  2.282237e-01,  2.226915e-01,  3.228747e-01,
E   4.235357e+00])

../.pybuild/cpython3_3.10_statsmodels/build/statsmodels/sandbox/regression/tests/test_gmm.py:207:
 AssertionError
--- End Message ---
--- Begin Message ---
Source: statsmodels
Source-Version: 0.13.2+dfsg-4
Done: Rebecca N. Palmer 

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

Debian distribution maintenance software
pp.
Rebecca N. Palmer  (supplier of updated statsmodels 
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: Sun, 24 Jul 2022 17:51:07 +0100
Source: statsmodels
Architecture: source
Version: 0.13.2+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Rebecca N. Palmer 
Closes: 1014884
Changes:
 statsmodels (0.13.2+dfsg-4) unstable; urgency=medium
 .
   * Tests: increase one error tolerance.  (Closes: #1014884)
   * Update Lintian override format (see #1007002).
   * Remove no longer needed Lintian / Salsa CI overrides.
Checksums-Sha1:
 dcdc0d68fd3ec8790c41595649ce0a6d59587f43 3597 statsmodels_0.13.2+dfsg-4.dsc
 09e6d58373771d3bc6d1c31dce7bb35a97c5 35744 
statsmodels_0.13.2+dfsg-4.debian.tar.xz
 15dac76e530f3c887346fc1250364a282b6589f9 6318 
statsmodels_0.13.2+dfsg-4_source.buildinfo
Checksums-Sha256:
 7956afe072a4413964c5390fb3b968d10ef09d9fd1a490bc59e5170d29f15810 3597 
statsmodels_0.13.2+dfsg-4.dsc
 3d0d5f8ae3c6ecd79641d2611c9f63b713adc901de9dad3ee525e753cdc9e894 35744 
statsmodels_0.13.2+dfsg-4.debian.tar.xz
 9c0968ee4d466dab8e8b6834ea6d645bb0bfabb085c01cb932385b72c6e35c31 6318 
statsmodels_0.13.2+dfsg-4_source.buildinfo
Files:
 50ed68faceabecea8a1ef75220083858 3597 python optional 
statsmodels_0.13.2+dfsg-4.dsc
 d026d4d0298a3582ccb18af5c6207560 35744 python optional 
statsmodels_0.13.2+dfsg-4.debian.tar.xz
 f2e9e60220f3926a3cb756b7a8d96b47 6318 python optional 
statsmodels_0.13.2+dfsg-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJMBAEBCgA2FiEEZ8sxEAXE7b4yF1MI3uUNDVZ+omYFAmLsQMYYHHJlYmVjY2Ff

Bug#1016668: kicad-packages3d - Unreachable maintainer

[Bastian Blank]

Source: kicad-packages3d
Version: 6.0.7-1
Severity: serious

Mails sent by the archive to the maintainer are rejected with the
following message:

| Action: failed
| Final-Recipient: rfc822;c.schoen...@t-online.de
| Status: 5.0.0
| Remote-MTA: dns; mx02.t-online.de
| Diagnostic-Code: smtp; 554 IP=194.177.211.212 - A problem occurred. (Ask your 
postmaster for help or to contact t...@rx.t-online.de to clarify.)

Bastian

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

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

Bug#1016667: Should this package be removed?

[Moritz Muehlenhoff]

Source: caldav-tester
Version: 7.0+20190225-4
Severity: serious

Your package came up as a candidate for removal from Debian:
The plan is to remove Python 2 in Bookworm and there's no
porting activity towards Python 3.

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz

Processed: Re: telepathy-salut: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

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

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

Bug#1016565: marked as done (liblibrecast0.5: Missing Breaks+Replaces headers against liblibrecast0.4: trying to overwrite '/usr/share/man/man3/lc_ctx_new.3.gz', which is also in package liblibrecast0

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 20:39:10 +
with message-id 
and subject line Bug#1016565: fixed in librecast 0.5.1-2
has caused the Debian Bug report #1016565,
regarding liblibrecast0.5: Missing Breaks+Replaces headers against 
liblibrecast0.4: trying to overwrite '/usr/share/man/man3/lc_ctx_new.3.gz', 
which is also in package liblibrecast0.4:amd64 0.4.5-1
to be marked as done.

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

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


-- 
1016565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblibrecast0.5
Severity: serious
Version: 0.5.1-1
Control: affects -1 lcsync

lcsync fails to upgrade due to this issue:

Unpacking liblibrecast0.5:amd64 (0.5.1-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/liblibrecast0.5_0.5.1-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man3/lc_ctx_new.3.gz', which is also in 
package liblibrecast0.4:amd64 0.4.5-1
Errors were encountered while processing:
 /var/cache/apt/archives/liblibrecast0.5_0.5.1-1_amd64.deb

There seem to be Breaks and Replaces headers missing for moving this and
potentially further files from liblibrecast0.4 to liblibrecast0.5.

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

Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: librecast
Source-Version: 0.5.1-2
Done: Vagrant Cascadian 

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

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated librecast package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Aug 2022 12:54:16 -0700
Source: librecast
Architecture: source
Version: 0.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Vagrant Cascadian 
Changed-By: Vagrant Cascadian 
Closes: 1016565
Changes:
 librecast (0.5.1-2) unstable; urgency=medium
 .
   * debian/patches: Make test 0012 time more robust.
   * debian/rules: Output the results of running the test suite.
   * debian/control: Add Breaks and Replaces on liblibrecast0.4. Thanks to
 Axel Beckert.  (Closes: #1016565)
   * debian/patches: Directly symlink the .so ABI version file.
Checksums-Sha1:
 f8a3bfcdc996eef673d58258b9fbe356637b69d5 1382 librecast_0.5.1-2.dsc
 b4b36fbec8948d0d47453d3a69dcff75d35a76bf 4856 librecast_0.5.1-2.debian.tar.xz
 f4a688650dd9987a34fca46260aa4afebb17fb20 5920 librecast_0.5.1-2_arm64.buildinfo
Checksums-Sha256:
 2f3310f16dfeed38173c24dfaf95813b5185233c91545b3b28a8289dec82e5c2 1382 
librecast_0.5.1-2.dsc
 8726935a9082d615feab8b8ab65a826d05a1434b60afeee9c78f7906e3fdd7f7 4856 
librecast_0.5.1-2.debian.tar.xz
 1f0f845ad870ed5fa648c0e49ddebeeda6b75a9c89841e3f910f11cf7165658a 5920 
librecast_0.5.1-2_arm64.buildinfo
Files:
 4c1d2007701af4a6d9c6c28e699a8672 1382 unknown optional librecast_0.5.1-2.dsc
 12e52fefa620273de1e3f2e05c4828e9 4856 unknown optional 
librecast_0.5.1-2.debian.tar.xz
 b0caaf089c26ef310a255bad3924c7dd 5920 unknown optional 
librecast_0.5.1-2_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iIkEARYKADEWIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCYuwqLxMcdmFncmFudEBk
ZWJpYW4ub3JnAAoJENxRj8h/lxaqOcoBAIHhPMyj2VYYqfSf+5OGeJZpPj8xeXcX
VfB89R1u961+AQCoSVx3S6EurIeLXvhIVDgjB1tXaFXOdxlq4aKE4x5sDQ==
=bNn6
-END PGP SIGNATURE End Message ---

Bug#1016261: marked as done (givaro: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 20:36:23 +
with message-id 
and subject line Bug#1016261: fixed in givaro 4.2.0-2
has caused the Debian Bug report #1016261,
regarding givaro: FTBFS: E: Build killed with signal TERM after 150 minutes of 
inactivity
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.)


-- 
1016261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: givaro
Version: 4.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> Parsing file /<>/tests/test-recint_convert.C...
> Preprocessing /<>/tests/test-recint_exp.C...
> Parsing file /<>/tests/test-recint_exp.C...
> Preprocessing /<>/tests/test-recint_extra.C...
> Parsing file /<>/tests/test-recint_extra.C...
> Preprocessing /<>/tests/test-recint_rand.C...
> Parsing file /<>/tests/test-recint_rand.C...
> Preprocessing /<>/tests/test-regression.C...
> Parsing file /<>/tests/test-regression.C...
> Preprocessing /<>/tests/test-ringarith.C...
> Parsing file /<>/tests/test-ringarith.C...
> Preprocessing /<>/tests/test-rint_arith.C...
> Parsing file /<>/tests/test-rint_arith.C...
> Preprocessing /<>/tests/test-rmint_arith.C...
> Parsing file /<>/g
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/givaro_4.2.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results

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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: givaro
Source-Version: 4.2.0-2
Done: Doug Torrance 

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

Debian distribution maintenance software
pp.
Doug Torrance  (supplier of updated givaro package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Aug 2022 16:04:02 -0400
Source: givaro
Built-For-Profiles: noudeb
Architecture: source
Version: 4.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Math Team 
Changed-By: Doug Torrance 
Closes: 1016261
Changes:
 givaro (4.2.0-2) unstable; urgency=medium
 .
   * debian/control
 - Bump Standards-Version to 4.6.1.
   * debian/copyright
 - Bump my copyright years.
   * debian/rules
 - Remove symlinks before building docs to avoid regression in doxygen
   1.9.4 (Closes: #1016261).
   * debian/salsa-ci.yml
 - Stop allowing reprotest to fail; no longer an issue with doxygen
   1.9.4.
Checksums-Sha1:
 4e2186552ffc6bd1b9d1b87b7db4763183ec1282 2391 givaro_4.2.0-2.dsc
 7b316a978a1d6dab2cfe0626be1d67eac1f07fd5 18688 givaro_4.2.0-2.debian.tar.xz
 0109c6ee85b3f26c0adec65bb35dbfac8a89aa06 8174 givaro_4.2.0-2_source.buildinfo
Checksums-Sha256:
 287942b1b12ab17091d37533e5978e16d8fda860db9176035af3950ad0875433 2391 
givaro_4.2.0-2.dsc
 12367530346407a1fa710e21e27c123e705d512b79157ef61d8024d787216485 18688 
givaro_4.2.0-2.debian.tar.xz
 64487f2e326c16ac243c00d5e7894a2f73434a238ff45dc1db8f141a8b9667f5 8174 
givaro_4.2.0-2_source.buildinfo
Files:
 6be2d8ff4a3d3d6045b9e36a0d62664c 2391 math optional givaro_4.2.0-2.dsc
 cf9d516182a195d769394fd7cdf314c9 18688 math optional 
givaro_4.2.0-2.debian.tar.xz
 0539949937754d1b65ebeb2e14fbd85b 8174 math optional 
givaro_4.2.0-2_source.buildinfo

Bug#1014575: marked as done (juce-modules-source: cmake error: missing /usr/lib/bin/JUCE-7.0.0/juce_lv2_helper)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 20:37:42 +
with message-id 
and subject line Bug#1014575: fixed in juce 7.0.1~ds0-1
has caused the Debian Bug report #1014575,
regarding juce-modules-source: cmake error: missing 
/usr/lib/bin/JUCE-7.0.0/juce_lv2_helper
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.)


-- 
1014575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: juce-modules-source
Version: 7.0.0~ds0-1
Severity: serious
Control: affects -1 src:iem-plugin-suite

Hi,

iem-plugin-suite/experimental recently started to FTBFS with a cmake error 
pointing to juce:

CMake Error at /usr/lib/x86_64-linux-gnu/cmake/JUCE-7.0.0/LV2_HELPER.cmake:79 
(message):
  The imported target "juce::juce_lv2_helper" references the file

 "/usr/lib/bin/JUCE-7.0.0/juce_lv2_helper"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/x86_64-linux-gnu/cmake/JUCE-7.0.0/LV2_HELPER.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/JUCE-7.0.0/JUCEConfig.cmake:57 (include)
  CMakeLists.txt:77 (find_package)


-- Configuring incomplete, errors occurred!


I'd suggest adding a minimal superficial autopkgtest to test cmake usability.
(You might take a look at the find_package(CUB) test in src:cub).


Andreas
--- End Message ---
--- Begin Message ---
Source: juce
Source-Version: 7.0.1~ds0-1
Done: IOhannes m zmölnig (Debian/GNU) 

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated juce 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 04 Aug 2022 22:02:56 +0200
Source: juce
Architecture: source
Version: 7.0.1~ds0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1014575
Changes:
 juce (7.0.1~ds0-1) unstable; urgency=medium
 .
   * New upstream version 7.0.1~ds0
   * Move juceaide/juce_lv2_helper to juce-modules-source
 + Install them into a private location
 + Declare versioned Breaks/Replaces against juce-tools
   * Fix path to juce_lv2_helper (Closes: #1014575)
   * Add autopkgtest for CMake snippets
 Thanks to Andreas Beckmann 
   * Install apiref via dh_installdocs
   * Run dh_doxygen after dh_installdocs
Checksums-Sha1:
 2ec649ce8b121e6f9804053e403e963a361e07fc 2646 juce_7.0.1~ds0-1.dsc
 1cfb13ad8d44facdbae5888085f1523855d98c06 10952696 juce_7.0.1~ds0.orig.tar.xz
 99b712f5c42917efbac66b305d9439294d0320d4 40152 juce_7.0.1~ds0-1.debian.tar.xz
Checksums-Sha256:
 ec3357beccf4571bcad78e3daeefaa21899bb9e5963f61e6b719dba176ab4109 2646 
juce_7.0.1~ds0-1.dsc
 67d4ffc727bc7219ecf684862926f2299b5bb7b29eec19cb90f42f7ac5fe73ba 10952696 
juce_7.0.1~ds0.orig.tar.xz
 a75cc2094465fb69103dda93c2ef9cf78f7d50e06defcce62ed3a58cba9dc0fc 40152 
juce_7.0.1~ds0-1.debian.tar.xz
Files:
 b6f3d8d227c7cf1c8308f7e49a78f4fd 2646 devel optional juce_7.0.1~ds0-1.dsc
 c4a529097ed811e35d9f061bc85e87c2 10952696 devel optional 
juce_7.0.1~ds0.orig.tar.xz
 817455fdece474e6f1c36ff7ee2b9783 40152 devel optional 
juce_7.0.1~ds0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmLsKCkWHGZvcnVtQHVt
bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+GmrD/4uszvuUaRe58RIs907Duxl/JZ0
byoGvID/gIkUQhuA1baToct7MDCht9/hGclzzf5lfn6uShGI9j/Kc8HzuA3fNTmg
dpbNgTfVPp/g4vPqL3lN5uxtwvZusXdrfe/bzsdz9VoYOrX+Gx1pgNU+SXU8PWv/
DmZh8AsN0NyeHWOoimzK9RFZdksDabwThh92C7m+LLCvulKRHq/4wHF92p4hZJCL
wmhYXQ9v9kpws8YAr7eM9AYbsUShlFukKRx65PQW5iw1kHJRHsQlKEdZ7CW/p/A6
8PEkjfoQ460gw58oPk6TwKj/xqVfd2axmvSFe7wX+hUuBtbm+XWcXHz54CODj7lb
nIfwLwGPvDrLdRkDjVV2vTcPzvODf98i42NA2C/c1TkeHmKpf6xDPMMBVWQCCCqq

Bug#1016209: Disregard last message

[Ignacio Vargas]

Nevermind, it was a mistake on my part. Bug is indeed resolved in mangohud
0.6.8-1

Bug#1016658: kalgebra: asserton failed on start

[karogyoker]

Package: kalgebra
Version: 4:20.12.1-1
Followup-For: Bug #1016658
X-Debbugs-Cc: karogyoker2+deb...@gmail.com

I've tried the same in a VM on a Haswell CPU.
I removed chromium related packages and installed epiphany-web.
These steps don't interfere with kalgebra.
Even before and after these steps kalgebra was working correctly.
It might have to do something with SSE2 or SSE3 maybe?

Bug#1016659: empathy: depends on libsoup2.4

[Jeremy Bicha]

Source: empathy
Version: 3.25.90+really3.12.14-2
Severity: serious

An app can't link against both libsoup2.4 and libsoup3 simultaneously.
empathy depends on libsoup2.4 but it also depends on several libraries
that will be switching to libsoup3.

There is no longer an upstream for empathy. Empathy was archived more
than a year ago which means bug reports, translation updates, and even
bugfixes are no longer being accepted.

https://gitlab.gnome.org/GNOME/empathy

We will likely need to remove Empathy from Debian soon.

Thank you,
Jeremy Bicha

Processed: Re: Move to templexxx-xorsimd? (Was: Bug#1002227: golang-github-templexxx-xor: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/templexxx/xor retur

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1002227 [src:golang-github-templexxx-xor] golang-github-templexxx-xor: 
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/templexxx/xor returned exit code 1
Severity set to 'important' from 'serious'

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

Bug#1011950: marked as done (pympress: Build-Depends: python3.9-doc)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 19:04:39 +
with message-id 
and subject line Bug#1011950: fixed in pympress 1.7.1-2
has caused the Debian Bug report #1011950,
regarding pympress: Build-Depends: python3.9-doc
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.)


-- 
1011950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pympress
Version: 1.7.1-1
Severity: important
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

pympress has a hardcoded build-dependency on python3.9-doc and will
FTBFS once Python 3.9 is removed from the archive.

Is it possible to change this to the generic python3-doc package from
src:python3-defaults?

Regards
Graham
--- End Message ---
--- Begin Message ---
Source: pympress
Source-Version: 1.7.1-2
Done: Christopher Hoskin 

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

Debian distribution maintenance software
pp.
Christopher Hoskin  (supplier of updated pympress package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Aug 2022 19:45:38 +0100
Source: pympress
Architecture: source
Version: 1.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Christopher Hoskin 
Closes: 1011950
Changes:
 pympress (1.7.1-2) unstable; urgency=medium
 .
   * Fix "Build-Depends: python3.9-doc" changed build dependency to python3-doc
 (Closes: #1011950)
Checksums-Sha1:
 984ac89ce3174981bb020baf5448761bbff451b8 2171 pympress_1.7.1-2.dsc
 6acad059412c345c13e11f8ac0aa0ff9039cf669 7884 pympress_1.7.1-2.debian.tar.xz
 4a0dcc4114114ff11691e985d22dfc68512b6303 8258 pympress_1.7.1-2_amd64.buildinfo
Checksums-Sha256:
 9ec29f28896f89fe7fdcee430e7138b0a6c04b0a871bd64732395dcb722a1a75 2171 
pympress_1.7.1-2.dsc
 afcb7dc0f0ca1cb9cc2f2e45132039919919f0eff85ab9db8302561dc33929a0 7884 
pympress_1.7.1-2.debian.tar.xz
 04833f375fb99fcd659ac72eef13c9b5f84ab05dbf8c184c19284a3b3978df88 8258 
pympress_1.7.1-2_amd64.buildinfo
Files:
 e751e00cc77396f2dd8760610e634e9a 2171 misc optional pympress_1.7.1-2.dsc
 47e0ea84a4d7dee5ccf5e4b028febcf4 7884 misc optional 
pympress_1.7.1-2.debian.tar.xz
 dfe0d91fd9dee2c6ea3e8d320187bef6 8258 misc optional 
pympress_1.7.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEbctJ5K6JlvFsvhGhf6qUsnUUSpoFAmLsFI0ACgkQf6qUsnUU
SprkEg//UJdmlJpR2Jjp1Vr+IiAB0nJLm+pfjubxJgBZQL1DO0MgVCyz6BG+b6vP
nX577f8UY6LxTcQxmBLYcmz8n5VYpob//ppKDU9pmBfqekQpV8ExMp+ZwXs4EiR1
m36+PFieb3nJJh4ohNgA86GeXiJD1xCBHiVhvTTvYLVXGVDnBVuX+Rz2LSHOyyF2
xy8hwzrTjnnt8xa1wkBxNrZ5ItQfYpG6bHGTenmx83lJEiSTFWhDtLeYhytLxEVX
jIxivORYDZnkyiTMDleuU5Vaay0NdpVJS9lGD96oMX2XVuxYjGMC6+iHC+LYi3AV
QFP2yGJVFJmlTLIt+Xc4he/zEfs1W6ogwCWqeWvakE3IkdmSOjhkyGXc/f/D6LE4
rOcpJuk3BpfyWH1BkWLDEKv/62uXL5pLmY/whyXHmNbDd4LYO2cHN4aPvrE6psLa
3dIgFECzGHQaMtkSiXN2bxu4RZfzAf6B5wLlVi5UmCms1SqnJZ5ryiTyUBYIEzkW
TaEdiow37BdKapRa6Gf84YipZ1JK6S7J7B92mCgmhloIkDIuUj4DNMe0O/Ssg8J7
K81ujrz4UkeqaDBHR3oHiG/tP3rvb+JDtchHFa9iDlqp/eKIBSEEpbeE3d3gaUB6
9akfXyoFrYC0rPGEw8DPAWkVgNXoXDxiAuqPWl8SVDpJOYRmHTU=
=+5Pi
-END PGP SIGNATURE End Message ---

Bug#1002227: Move to templexxx-xorsimd? (Was: Bug#1002227: golang-github-templexxx-xor: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/templexxx/xor returne

[Nilesh Patra]

Control: severity -1 important

I am uploading a new revision shortly disabling this
test so it allows revdeps to migrate atleast most which have nothing
to do with the failing function test in question.

Will go ahead with packaging xorsimd in next weeks (occupied with RL)
unless no-one beats me to it.

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1013080: marked as done (dask: incompatibility with scipy 1.8)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 19:03:54 +
with message-id 
and subject line Bug#1013080: fixed in dask 2022.02.0+dfsg-1
has caused the Debian Bug report #1013080,
regarding dask: incompatibility with scipy 1.8
to be marked as done.

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

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


-- 
1013080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dask
Version: 2022.01.0+dfsg-2
Severity: normal
Control: tags -1 patch

dask 2022.01 uses a deprecated scipy API and now fails tests with
scipy 1.8.1:

_ test_one[chisquare] __

kind = 'chisquare'

@pytest.mark.parametrize(
"kind", ["chisquare", "power_divergence", "normaltest", "skewtest", 
"kurtosistest"]
)
def test_one(kind):
a = np.random.random(size=30)
a_ = da.from_array(a, 3)

dask_test = getattr(dask.array.stats, kind)
scipy_test = getattr(scipy.stats, kind)

>   result = dask_test(a_)

/usr/lib/python3/dist-packages/dask/array/tests/test_stats.py:56: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/dask/array/stats.py:136: in chisquare
return power_divergence(f_obs, f_exp=f_exp, ddof=ddof, axis=axis, 
lambda_="pearson")
/usr/lib/python3/dist-packages/dask/array/stats.py:144: in power_divergence
if lambda_ not in scipy.stats.stats._power_div_lambda_names:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

name = '_power_div_lambda_names'

def __getattr__(name):
if name not in __all__:
>   raise AttributeError(
"scipy.stats.stats is deprecated and has no attribute "
f"{name}. Try looking in scipy.stats instead.")
E   AttributeError: scipy.stats.stats is deprecated and has no 
attribute _power_div_lambda_names. Try looking in scipy.stats instead.

/usr/lib/python3/dist-packages/scipy/stats/stats.py:54: AttributeError


Likewise
test_two[chisquare-kwargs4]
test_two[power_divergence-kwargs8]
test_power_divergence_invalid


The incompatibility is fixed in dask 2022.03 (lastest is 2022.6),
or apply the patch in PR#8694
https://github.com/dask/dask/pull/8694





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

Kernel: Linux 5.18.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: dask
Source-Version: 2022.02.0+dfsg-1
Done: Diane Trout 

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

Debian distribution maintenance software
pp.
Diane Trout  (supplier of updated dask package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Aug 2022 11:15:42 -0700
Source: dask
Architecture: source
Version: 2022.02.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Diane Trout 
Closes: 1013080
Changes:
 dask (2022.02.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream release
   * Refresh patches
   * split tests/control Tests-Command: into a separate shell script
   * Add sphinx-remove-toctree and sphinx-tabs to build-depends
   * add 32-bit compatibility patch for pandas 1.3
 See https://github.com/dask/dask/issues/8169
   * Copy conftest.py into test directory for autopkgtests
   * Add python3-ipython as a build-dependency.
 - it provides a sphinx formatting extension.
   * Add patch pytest-futurewarning.patch for compatibility with our pytest
   * Add scipy-1.8.patch (Closes: #1013080) for Scipy 1.8 compatibility
 Thanks: Graham Inggs
   * run autopkgtest on all supported versions
   * Remove built-using on -doc package

Bug#1016261: givaro: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Torrance, Douglas]

On Fri, 29 Jul 2022 18:33:25 +0200 Lucas Nussbaum  wrote:

Source: givaro
Version: 4.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> Parsing file /<>/tests/test-recint_convert.C...
> Preprocessing /<>/tests/test-recint_exp.C...
> Parsing file /<>/tests/test-recint_exp.C...
> Preprocessing /<>/tests/test-recint_extra.C...
> Parsing file /<>/tests/test-recint_extra.C...
> Preprocessing /<>/tests/test-recint_rand.C...
> Parsing file /<>/tests/test-recint_rand.C...
> Preprocessing /<>/tests/test-regression.C...
> Parsing file /<>/tests/test-regression.C...
> Preprocessing /<>/tests/test-ringarith.C...
> Parsing file /<>/tests/test-ringarith.C...
> Preprocessing /<>/tests/test-rint_arith.C...
> Parsing file /<>/tests/test-rint_arith.C...
> Preprocessing /<>/tests/test-rmint_arith.C...
> Parsing file /<>/g
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/givaro_4.2.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results

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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.



I think this is really a regression in Doxygen (version 1.9.4 was just uploaded
recently).  I've reported it at https://github.com/doxygen/doxygen/issues/9491.

An hacky fix is to remove the symlinks that are generated by the configure
script before building the documentation.  I'll upload a new package shortly.

Doug


signature.asc
Description: PGP signature

Bug#1016658: kalgebra: fails to start: assertion failed

[karogyoker]

Package: kalgebra
Version: 4:20.12.1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: karogyoker2+deb...@gmail.com

Dear Maintainer,

I use Debian Edu 11.4 Standard install for i386 on an Athlon XP.
When I try to start kalgebra from Terminal, this is what I get:

(kalgebra:3838): Gtk-CRITICAL **: 14:28:36.532: 
_gtk_css_ease_value_new_cubic_bezier: assertion 'x1 <= 1.0' failed

(kalgebra:3838): Gtk-CRITICAL **: 14:28:36.534: _gtk_css_array_value_new: 
assertion 'content != NULL' failed
**
Gtk:ERROR:../../../../gtk/gtkcssstylepropertyimpl.c:87:gtk_css_style_property_register:
 assertion failed: (initial_value != NULL)
Bail out! 
Gtk:ERROR:../../../../gtk/gtkcssstylepropertyimpl.c:87:gtk_css_style_property_register:
 assertion failed: (initial_value != NULL)
Aborted


-- System Information:
Debian Release: 11.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 5.10.0-16-686-pae (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kalgebra depends on:
ii  kalgebra-common  4:20.12.1-1
ii  kio  5.78.0-5
ii  libanalitza8 4:20.12.0-2
ii  libanalitzagui8  4:20.12.0-2
ii  libanalitzaplot8 4:20.12.0-2
ii  libanalitzawidgets8  4:20.12.0-2
ii  libc62.31-13+deb11u3
ii  libkf5configcore55.78.0-4
ii  libkf5configwidgets5 5.78.0-2
ii  libkf5coreaddons55.78.0-4
ii  libkf5i18n5  5.78.0-2
ii  libkf5kiocore5   5.78.0-5
ii  libkf5widgetsaddons5 5.78.0-2
ii  libkf5xmlgui55.78.0-2
ii  libqt5core5a 5.15.2+dfsg-9
ii  libqt5gui5   5.15.2+dfsg-9
ii  libqt5webenginewidgets5  5.15.2+dfsg-3
ii  libqt5widgets5   5.15.2+dfsg-9
ii  libreadline8 8.1-1
ii  libstdc++6   10.2.1-6

kalgebra recommends no packages.

kalgebra suggests no packages.

-- no debconf information

Bug#1011815: marked as done (pympress: FTBFS: ModuleNotFoundError: No module named 'attr')

[Debian Bug Tracking System]

Your message dated Thu, 4 Aug 2022 19:19:39 +0100
with message-id 

and subject line Done
has caused the Debian Bug report #1011815,
regarding pympress: FTBFS: ModuleNotFoundError: No module named 'attr'
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.)


-- 
1011815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pympress
Version: 1.7.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:239: /usr/bin/python3.9 setup.py build 
> Using setuptools.setup():
> running build
> running build_py
> running compile_catalog
> 197 of 255 messages (77%) translated in 
> pympress/share/locale/cs/LC_MESSAGES/pympress.po
> compiling catalog pympress/share/locale/cs/LC_MESSAGES/pympress.po to 
> pympress/share/locale/cs/LC_MESSAGES/pympress.mo
> 151 of 255 messages (59%) translated in 
> pympress/share/locale/pl/LC_MESSAGES/pympress.po
> compiling catalog pympress/share/locale/pl/LC_MESSAGES/pympress.po to 
> pympress/share/locale/pl/LC_MESSAGES/pympress.mo
> 195 of 255 messages (76%) translated in 
> pympress/share/locale/es/LC_MESSAGES/pympress.po
> compiling catalog pympress/share/locale/es/LC_MESSAGES/pympress.po to 
> pympress/share/locale/es/LC_MESSAGES/pympress.mo
> 251 of 255 messages (98%) translated in 
> pympress/share/locale/fr/LC_MESSAGES/pympress.po
> compiling catalog pympress/share/locale/fr/LC_MESSAGES/pympress.po to 
> pympress/share/locale/fr/LC_MESSAGES/pympress.mo
> 166 of 255 messages (65%) translated in 
> pympress/share/locale/de/LC_MESSAGES/pympress.po
> compiling catalog pympress/share/locale/de/LC_MESSAGES/pympress.po to 
> pympress/share/locale/de/LC_MESSAGES/pympress.mo
> creating /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/extras.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/util.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/__main__.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/scribble.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/app.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/dialog.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/surfacecache.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/ui.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/pointer.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/builder.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/editable_label.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/talk_time.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/config.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/document.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> creating 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/media_overlays
> copying pympress/media_overlays/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/media_overlays
> copying pympress/media_overlays/gst_backend.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/media_overlays
> copying pympress/media_overlays/base.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/media_overlays
> copying pympress/media_overlays/vlc_backend.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/media_overlays
> copying pympress/media_overlays/gif_backend.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/media_overlays
> creating /<>/.pybuild/cpython3_3.9_pympress/build/pympress/share
> copying pympress/share/defaults.conf -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/share
> creating 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/share/xml
> copying pympress/share/xml/highlight.glade -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/share/xml
> copying pympress/share/xml/content.glade -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/share/xml
> copying pympress/share/xml/presenter.glade -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/share/xml
> copying 

Processed: [bts-link] source package spdlog

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package spdlog
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1015742 (http://bugs.debian.org/1015742)
> # Bug title: libspdlog1: ABI breakage without SONAME bump
> #  * https://github.com/gabime/spdlog/issues/2454
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1015742 + fixed-upstream
Bug #1015742 [libspdlog1] libspdlog1: ABI breakage without SONAME bump
Bug #1016408 [libspdlog1] libspdlog1: ABI breakage without SONAME bump
Bug #1016466 [libspdlog1] libspdlog1: ABI breakage without SONAME bump
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 1015742 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #1016408 (http://bugs.debian.org/1016408)
> # Bug title: libspdlog1: ABI breakage without SONAME bump
> #  * https://github.com/gabime/spdlog/issues/2454
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1016408 + fixed-upstream
Bug #1016408 [libspdlog1] libspdlog1: ABI breakage without SONAME bump
Bug #1015742 [libspdlog1] libspdlog1: ABI breakage without SONAME bump
Bug #1016466 [libspdlog1] libspdlog1: ABI breakage without SONAME bump
Ignoring request to alter tags of bug #1016408 to the same tags previously set
Ignoring request to alter tags of bug #1015742 to the same tags previously set
Ignoring request to alter tags of bug #1016466 to the same tags previously set
> usertags 1016408 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package openssl

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package openssl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1016290 (http://bugs.debian.org/1016290)
> # Bug title: openssl: EC code appears to be broken on s390x
> #  * https://github.com/openssl/openssl/issues/18912
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1016290 + fixed-upstream
Bug #1016290 [openssl] openssl: EC code appears to be broken on s390x
Added tag(s) fixed-upstream.
> usertags 1016290 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:golang-github-traefik-yaegi

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package 
> src:golang-github-traefik-yaegi
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1008421 (http://bugs.debian.org/1008421)
> # Bug title: golang-github-traefik-yaegi: FTBFS with Go > 1.18
> #  * https://github.com/traefik/yaegi/issues/1363
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1008421 + fixed-upstream
Bug #1008421 [src:golang-github-traefik-yaegi] golang-github-traefik-yaegi: 
FTBFS with Go > 1.18
Added tag(s) fixed-upstream.
> usertags 1008421 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1008421 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:statsmodels

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:statsmodels
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1014278 (http://bugs.debian.org/1014278)
> # Bug title: statsmodels: s390x fails TestDynamicFactor test_mle with scipy 
> 1.8 and pythran
> #  * https://github.com/statsmodels/statsmodels/issues/8341
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1014278 + fixed-upstream
Bug #1014278 [src:statsmodels] statsmodels: s390x fails TestDynamicFactor 
test_mle with scipy 1.8 and pythran
Added tag(s) fixed-upstream.
> usertags 1014278 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1014278 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #1014884 (http://bugs.debian.org/1014884)
> # Bug title: statsmodels: FTBFS on mipsel (pythran shifted tolerances)
> #  * https://github.com/statsmodels/statsmodels/issues/8341
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1014884 + fixed-upstream
Bug #1014884 [src:statsmodels] statsmodels: FTBFS on mipsel (pythran shifted 
tolerances)
Added tag(s) fixed-upstream.
> usertags 1014884 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1014884 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#1013073: marked as done (ypserv: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 17:07:06 +
with message-id 
and subject line Bug#1013073: fixed in ypserv 4.2-1
has caused the Debian Bug report #1013073,
regarding ypserv: ftbfs with GCC-12
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.)


-- 
1013073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ypserv
Version: 4.1-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

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-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/ypserv_4.1-2_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
config.status: creating scripts/ypinit
config.status: creating scripts/ypMakefile
config.status: creating config.h
config.status: executing depfiles commands

Configuration:

  Source code location:   .
  Compiler:   gcc
  Compiler flags: -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -W -Wall 
-Wbad-function-cast -Wcast-align -Wcast-qual -Wmissing-declarations 
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes
  Preprocessor:   gcc -E
  Preprocessor flags: -Wdate-time -D_FORTIFY_SOURCE=2
  Libraries:   -lgdbm -lcrypt -lsystemd -ltirpc -lnsl -ltirpc
  Awk:/usr/bin/mawk
  Shell:  /bin/bash
  NIS map dir:/var/yp
  Install path prefix:/usr
  Install ypserv.conf in:  /etc
  Allow root password: yes
  Use FQDN as master name: 1
  Notify systemd:  1

for f in `find /<> -name '*.8.xml'`; \
do d=`dirname $f`; n=`basename $f .xml`; [ -f /<>/$d/$n ] 
|| cp -f /<>/debian/man/$n $d/.; done 
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j8
make[1]: Entering directory '/<>'
/usr/bin/gmake  all-recursive
gmake[2]: Entering directory '/<>'
Making all in etc
gmake[3]: Entering directory '/<>/etc'
gmake[3]: Nothing to be done for 'all'.
gmake[3]: Leaving directory '/<>/etc'
Making all in lib
gmake[3]: Entering directory '/<>/lib'
gcc -DHAVE_CONFIG_H -D_REENTRANT=1 -DCONFDIR=\"/etc\" -DYPMAPDIR=\"/var/yp\" 
-DUSE_SD_NOTIFY=1 -I. -I..  -I.. -I.. -I. -Wdate-time -D_FORTIFY_SOURCE=2 -fpie 
-I/usr/include/tirpc -I/usr/include/tirpc -Werror -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -W -Wall -Wbad-function-cast -Wcast-align -Wcast-qual 
-Wmissing-declarations -Wmissing-prototypes -Wpointer-arith -Wreturn-type 
-Wstrict-prototypes -c -o log_msg.o log_msg.c
gcc -DHAVE_CONFIG_H -D_REENTRANT=1 -DCONFDIR=\"/etc\" -DYPMAPDIR=\"/var/yp\" 
-DUSE_SD_NOTIFY=1 -I. -I..  -I.. -I.. -I. -Wdate-time -D_FORTIFY_SOURCE=2 -fpie 
-I/usr/include/tirpc -I/usr/include/tirpc -Werror -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -W -Wall -Wbad-function-cast -Wcast-align -Wcast-qual 
-Wmissing-declarations -Wmissing-prototypes -Wpointer-arith -Wreturn-type 
-Wstrict-prototypes -c -o ypserv_conf.o ypserv_conf.c
gcc -DHAVE_CONFIG_H -D_REENTRANT=1 -DCONFDIR=\"/etc\" -DYPMAPDIR=\"/var/yp\" 
-DUSE_SD_NOTIFY=1 -I. -I..  -I.. -I.. -I. -Wdate-time -D_FORTIFY_SOURCE=2 -fpie 
-I/usr/include/tirpc -I/usr/include/tirpc -Werror -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 

Bug#1009806: Bug report - forced mount parameters

[Chris Hofstaedtler]

Control: severity -1 normal
Control: tags -1 + moreinfo

* Mcgiwer :
> I had discovered an very annoying and serious bug in the "mount" package:
> 
> While attempting to mount a hard disk while beeing logged in locally in 
> terminal (as root), the mount command forces following mount options:
> 
> "nosuid,nodev,noexec"
> 
> totally ignoring the ones I give.

I cannot reproduce this problem.

> It's at latest that good that it does not mount it as write-only (without 
> possibility to read from it).

I do not understand what you are saying here.

Chris

Processed: Re: Bug#1009806: Bug report - forced mount parameters

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1009806 [mount] Bug report - forced mount parameters
Severity set to 'normal' from 'critical'
> tags -1 + moreinfo
Bug #1009806 [mount] Bug report - forced mount parameters
Added tag(s) moreinfo.

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

Bug#1012895: cwidget RC bug: Please upload or grant me cwidget team membership on Salsa

[Axel Beckert]

Hi Manuel,

TL;DR: Please grant me cwidget team membership on Salsa so we don't
have to NMU it. Or just do an upload of cwidget with the patch from
#1015925.

I know you're busy with RISC-V and other stuff, but please do me a
small favour and add me to the cwidget team on Salsa, probably via
https://salsa.debian.org/groups/cwidget-team/-/group_members

Background:

There are currently RC bugs in aptitude and cwidget which both cause
aptitude to FTBFS with GCC 12:

  https://bugs.debian.org/1015925
  https://bugs.debian.org/1012895

Both bug reports have patches by pabs (Cc'ed).

Without having the cwidget bugs (#1015925) fixed, I can't fix the
aptitude one (#1012895).

Currently you're the only "cwidget team" member on Salsa. I've
requested team membership there a few days ago, so I can do proper
"Team uploads" for cwidget, too. Otherwise pabs or me would have to
NMU cwidget. And I think having a second uploader for cwidget would be
good in the long run anyway, especially because aptitude is its only
library user.

Other options beside the NMU are (obviously) that you do a quick
upload of cwidget with pabs' patch from #1015925.

(Sent from my non-debian address to your non-debian address due to the
current GMail fuckup which causes tons of false positive mail
rejections by GMail, especially with mails forwarded by the BTS.)

Kind regards, Axel
-- 
PGP: 2FF9CD59612616B5  /~\  Plain Text Ribbon Campaign, http://arc.pasp.de/
Mail: a...@deuxchevaux.org  \ /  Say No to HTML in E-Mail and Usenet
Mail+Jabber: a...@noone.org  X
https://axel.beckert.ch/   / \  I love long mails: https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#1014575: marked as pending in juce

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

Bug #1014575 in juce 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/multimedia-team/juce/-/commit/3e7f9152cba12cc985ca3b07ce8c68c31324f2a4


Fix path to juce_lv2_helper

Closes: #1014575


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1014575

Processed: Bug#1014575 marked as pending in juce

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1014575 [juce-modules-source] juce-modules-source: cmake error: missing 
/usr/lib/bin/JUCE-7.0.0/juce_lv2_helper
Added tag(s) pending.

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

Bug#1016648: hedgewars FTBFS with ffmpeg 5

[Peter Green]

Package: hedgewars
Version: 1.0.0-16
Severity: serious

Hedgewars failed to build on all architectures when binnmu'd (note: the binnmu 
sat
in BD-Uninstallable for a long time due to issues with haskell packages).


[ 41%] Linking Pascal executable ../bin/hwengine
cd /<>/obj-x86_64-linux-gnu/hedgewars && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/hwengine.dir/link.txt --verbose=1
/<>/obj-x86_64-linux-gnu/bin/ppas.sh
Linking /<>/obj-x86_64-linux-gnu/bin/hwengine
/usr/bin/ld.bfd: /<>/obj-x86_64-linux-gnu/bin//libavwrapper.so: 
undefined reference to `avcodec_encode_audio2'
/usr/bin/ld.bfd: /<>/obj-x86_64-linux-gnu/bin//libavwrapper.so: 
undefined reference to `avcodec_get_context_defaults3'
/usr/bin/ld.bfd: /<>/obj-x86_64-linux-gnu/bin//libavwrapper.so: 
undefined reference to `avcodec_encode_video2'
An error occurred while linking 
/<>/obj-x86_64-linux-gnu/bin/hwengine
make[3]: *** [hedgewars/CMakeFiles/hwengine.dir/build.make:165: bin/hwengine] 
Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:2688: hedgewars/CMakeFiles/hwengine.dir/all] 
Error 2
make[2]: *** Waiting for unfinished jobs

Bug#1016346: [Help] LaTeX error due to encoding issues (Was: Bug#1016346: pycorrfit: FTBFS: make[1]: *** [debian/rules:46: override_dh_auto_build] Error 1)

[Andreas Tille]

Control: tags -1 help

Hi,

Am Fri, Jul 29, 2022 at 08:41:23PM +0200 schrieb Lucas Nussbaum:
> > (/usr/share/texlive/texmf-dist/tex/latex/ucs/data/uni-0.def)
> > No file PyCorrFit_doc.toc.
> > ! Argument of ? has an extra }.
> >  
> > \par 
> > l.144 \newpage

I was able to reproduce this error with the small LaTeX file:


$ cat test.tex
\documentclass[]{scrartcl}
\usepackage[utf8x]{inputenc}
\usepackage{hyperref}
\begin{document}
Bla
\end{document}

$ pdflatex test.tex
...
(/usr/share/texlive/texmf-dist/tex/generic/uniquecounter/uniquecounter.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def)
(./PyCorrFit_doc.aux) (/usr/share/texlive/texmf-dist/tex/latex/ucs/ucsencs.def)
(./PyCorrFit_doc.out) (./PyCorrFit_doc.out)
(/usr/share/texlive/texmf-dist/tex/latex/bookmark/bookmark.sty
(/usr/share/texlive/texmf-dist/tex/latex/bookmark/bkm-pdftex.def))
! Argument of � has an extra }.
 
\par 
l.6 \end{document}
  
? 
! Emergency stop.
 
\par 
l.6 \end{document}
  
!  ==> Fatal error occurred, no output PDF file produced!


If I subsitute  s/utf8x/utf8/  in line 2  the test file builds fine.
However, in the full LaTeX source fails later with:

...
See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...  
  
l.288 Name & \textbf{TIR (□x$\upsigma$/Exp.) 3D}


So if someone finds a clue how to build this file properly


\documentclass[]{scrartcl}
\usepackage[utf8]{inputenc}
\usepackage{hyperref}
\begin{document}
Bla \textbf{TIR (□x$\upsigma$/Exp.) 3D}
\end{document}


the bug can be fixed.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Processed: [Help] LaTeX error due to encoding issues (Was: Bug#1016346: pycorrfit: FTBFS: make[1]: *** [debian/rules:46: override_dh_auto_build] Error 1)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #1016346 [src:pycorrfit] pycorrfit: FTBFS: make[1]: *** [debian/rules:46: 
override_dh_auto_build] Error 1
Added tag(s) help.

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

Bug#1014417: meson: test changes causes FTBFS

[Jeremy Bicha]

gjs 1.73 made changes so that it builds now with meson 0.63.

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

Ubuntu cherry-picked some merge proposals that enabled gjs 1.72 to build too.

http://launchpadlibrarian.net/614996822/meson_0.63.0-1_0.63.0-1ubuntu3.diff.gz

Thank you,
Jeremy Bicha

Bug#1016297: marked as done (libstatgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 13:34:06 +
with message-id 
and subject line Bug#1016297: fixed in libstatgen 1.0.15-6
has caused the Debian Bug report #1016297,
regarding libstatgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
to be marked as done.

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

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


-- 
1016297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libstatgen
Version: 1.0.15-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p debian/libstatgen-dev/usr/include/libStatGen/
> cp -L include/* debian/libstatgen-dev/usr/include/libStatGen/
> ln -s libStatGen.so.1 libStatGen.so
> d-shlibmove --commit \
> --multiarch \
> --devunversioned \
> --exclude-a \
> libStatGen.so
> Library package automatic movement utility
> set -e
> install -d -m 755 debian/libstatgen-dev/usr/lib/x86_64-linux-gnu
> install -d -m 755 debian/libstatgen1/usr/lib/x86_64-linux-gnu
> mv ./libStatGen.la debian/libstatgen-dev/usr/lib/x86_64-linux-gnu || true
> mv ./libStatGen.so debian/libstatgen-dev/usr/lib/x86_64-linux-gnu
> mv /<>/libStatGen.so.1 
> debian/libstatgen1/usr/lib/x86_64-linux-gnu
> PKGDEV=libstatgen-dev
> PKGSHL=libstatgen1
> mv: cannot stat './libStatGen.la': No such file or directory
> make[1]: Leaving directory '/<>'
>dh_installdocs -O--no-parallel
>dh_installchangelogs -O--no-parallel
>dh_installsystemduser -O--no-parallel
>dh_perl -O--no-parallel
>dh_link -O--no-parallel
>dh_strip_nondeterminism -O--no-parallel
>dh_compress -O--no-parallel
>dh_fixperms -O--no-parallel
>dh_missing -O--no-parallel
>dh_dwz -a -O--no-parallel
>dh_strip -a -O--no-parallel
>dh_makeshlibs -a -O--no-parallel
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libstatgen1/DEBIAN/symbols doesn't match 
> completely debian/libstatgen1.symbols
> --- debian/libstatgen1.symbols (libstatgen1_1.0.15-5_amd64)
> +++ dpkg-gensymbolsh3JD9Q 2022-07-29 09:31:11.378115176 +
> @@ -1636,6 +1636,7 @@
>   _ZN9FastQFile11interleavedEv@Base 1.0.15
>   _ZNK13VcfRecordInfo11getInfoPairB5cxx11Ei@Base 1.0.15
>   
> _ZNKSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE4findERKS5_@Base
>  1.0.14
> + 
> _ZNSt10_HashtableINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_SaIS5_ENSt8__detail9_IdentityESt8equal_toIS5_ESt4hashIS5_ENS7_18_Mod_range_hashingENS7_20_Default_ranged_hashENS7_20_Prime_rehash_policyENS7_17_Hashtable_traitsILb1ELb1ELb14findERKS5_@Base
>  1.0.15-5
>   
> _ZNSt10_HashtableINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_SaIS5_ENSt8__detail9_IdentityESt8equal_toIS5_ESt4hashIS5_ENS7_18_Mod_range_hashingENS7_20_Default_ranged_hashENS7_20_Prime_rehash_policyENS7_17_Hashtable_traitsILb1ELb1ELb19_M_rehashEmRKm@Base
>  1.0.15
>   _ZNSt12_Destroy_auxILb0EE9__destroyIP6StringEEvT_S4_@Base 1.0.14
>   _ZNSt12_Destroy_auxILb0EE9__destroyIPN9IndexBase9ReferenceEEEvT_S5_@Base 
> 1.0.14
> @@ -1649,7 +1650,7 @@
>   _ZNSt12_Vector_baseIfSaIfEED2Ev@Base 1.0.14
>   _ZNSt12_Vector_baseIiSaIiEED1Ev@Base 1.0.14
>   _ZNSt12_Vector_baseIiSaIiEED2Ev@Base 1.0.14
> - 
> _ZNSt22__uninitialized_fill_nILb0EE15__uninit_fill_nIPSt6vectorIbSaIbEEmS4_EET_S6_T0_RKT1_@Base
>  1.0.14
> +#MISSING: 1.0.15-5# 
> _ZNSt22__uninitialized_fill_nILb0EE15__uninit_fill_nIPSt6vectorIbSaIbEEmS4_EET_S6_T0_RKT1_@Base
>  1.0.14
>   
> _ZNSt6vectorIP12SamHeaderTagSaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
>  1.0.14
>   
> _ZNSt6vectorIcSaIcEE17_M_realloc_insertIJcEEEvN9__gnu_cxx17__normal_iteratorIPcS1_EEDpOT_@Base
>  1.0.14
>   
> _ZNSt6vectorIfSaIfEE17_M_realloc_insertIJRKfEEEvN9__gnu_cxx17__normal_iteratorIPfS1_EEDpOT_@Base
>  1.0.14
> @@ -1660,6 +1661,12 @@
>   _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC1IS3_EEPKcRKS3_@Base 
> 1.0.15
>   _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC2IS3_EEPKcRKS3_@Base 
> 1.0.15
>   _ZNSt7__cxx119to_stringEx@Base 1.0.15
> + 
> 

Bug#1013667: marked as done (virt-manager: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 13:07:31 +
with message-id 
and subject line Bug#1013667: fixed in virt-manager 1:4.0.0-3
has caused the Debian Bug report #1013667,
regarding virt-manager: FTBFS: tests failed
to be marked as done.

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

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


-- 
1013667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: virt-manager
Version: 1:4.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> pytest-3 -v -rs
> = test session starts 
> ==
> platform linux -- Python 3.10.5, pytest-6.2.5, py-1.10.0, pluggy-1.0.0 -- 
> /usr/bin/python3
> cachedir: .pytest_cache
> rootdir: /<>, configfile: setup.cfg, testpaths: tests/
> collecting ... collected 541 items
> 
> tests/test_capabilities.py::testCapsCPUFeaturesNewSyntax PASSED  [  
> 0%]
> tests/test_capabilities.py::testCapsUtilFuncs PASSED [  
> 0%]
> tests/test_capabilities.py::testDomainCapabilities PASSED[  
> 0%]
> tests/test_capabilities.py::testDomainCapabilitiesx86 PASSED [  
> 0%]
> tests/test_capabilities.py::testDomainCapabilitiesAArch64 PASSED [  
> 0%]
> tests/test_cloner.py::test_clone_unmanaged PASSED[  
> 1%]
> tests/test_cloner.py::test_generate_name PASSED  [  
> 1%]
> tests/test_conn.py::test_misc PASSED [  
> 1%]
> tests/test_conn.py::test_default_uri PASSED  [  
> 1%]
> tests/test_conn.py::test_poll PASSED [  
> 1%]
> tests/test_disk.py::test_disk_numtotarget PASSED [  
> 2%]
> tests/test_disk.py::test_disk_dir_searchable PASSED  [  
> 2%]
> tests/test_disk.py::test_disk_path_in_use_kernel PASSED  [  
> 2%]
> tests/test_disk.py::test_disk_diskbackend_misc PASSED[  
> 2%]
> tests/test_disk.py::test_disk_diskbackend_parse PASSED   [  
> 2%]
> tests/test_disk.py::test_disk_rbd_path PASSED[  
> 2%]
> tests/test_misc.py::test_misc_cpu_topology PASSED[  
> 3%]
> tests/test_misc.py::test_misc_guest_osinfo_metadata PASSED   [  
> 3%]
> tests/test_misc.py::test_misc_nonpredicatble_generate PASSED [  
> 3%]
> tests/test_misc.py::test_misc_support_cornercases PASSED [  
> 3%]
> tests/test_misc.py::test_misc_osxml_cornercases PASSED   [  
> 3%]
> tests/test_misc.py::test_misc_cpu_cornercases PASSED [  
> 4%]
> tests/test_misc.py::test_misc_meter PASSED   [  
> 4%]
> tests/test_nodedev.py::testFunkyChars PASSED [  
> 4%]
> tests/test_nodedev.py::testNetDevice PASSED  [  
> 4%]
> tests/test_nodedev.py::testPCIDevice PASSED  [  
> 4%]
> tests/test_nodedev.py::testUSBDevDevice PASSED   [  
> 4%]
> tests/test_nodedev.py::testSCSIDevice PASSED [  
> 5%]
> tests/test_nodedev.py::testStorageDevice PASSED  [  
> 5%]
> tests/test_nodedev.py::testSCSIBus PASSED[  
> 5%]
> tests/test_nodedev.py::testDRMDevice PASSED  [  
> 5%]
> tests/test_nodedev.py::testDASDMdev PASSED   [  
> 5%]
> tests/test_nodedev.py::testAPQNMdev PASSED   [  
> 6%]
> tests/test_nodedev.py::testPCIMdev PASSED[  
> 6%]
> tests/test_nodedev.py::testPCIMdevNewFormat PASSED   [  
> 6%]
> tests/test_nodedev.py::testNodeDev2USB1 PASSED   [  
> 6%]
> tests/test_nodedev.py::testNodeDev2USB2 PASSED   [  
> 6%]
> tests/test_nodedev.py::testNodeDev2PCI PASSED[  
> 7%]
> tests/test_nodedev.py::testNodeDevFail PASSED[  
> 7%]
> tests/test_osdict.py::test_list_os PASSED[  
> 7%]
> tests/test_osdict.py::test_recommended_resources PASSED  [  
> 7%]
> tests/test_osdict.py::test_urldetct_matching_distros PASSED   

Bug#1016293: marked as done (spoa: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 12:48:59 +
with message-id 
and subject line Bug#1016293: fixed in spoa 4.0.7+ds-3
has caused the Debian Bug report #1016293,
regarding spoa: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
to be marked as done.

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

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


-- 
1016293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spoa
Version: 4.0.7+ds-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> d-shlibmove --commit \
>   --multiarch \
>   --devunversioned \
>   --exclude-la \
>   --exclude-a \
>   --movedev debian/tmp/usr/include/spoa usr/include \
>   --movedev debian/tmp/usr/lib/*/pkgconfig usr/lib/x86_64-linux-gnu \
>   debian/tmp/usr/lib/*/*.so
> Library package automatic movement utility
> set -e
> install -d -m 755 debian/libspoa-dev/usr/lib/x86_64-linux-gnu
> install -d -m 755 debian/libspoa7.0.0/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/libspoa.so 
> debian/libspoa-dev/usr/lib/x86_64-linux-gnu
> mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libspoa.so.7.0.0 
> debian/libspoa7.0.0/usr/lib/x86_64-linux-gnu
> PKGDEV=libspoa-dev
> PKGSHL=libspoa7.0.0
> install -d -m 755 debian/libspoa-dev/usr/include
> mv debian/tmp/usr/include/spoa debian/libspoa-dev/usr/include
> install -d -m 755 debian/libspoa-dev/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig 
> debian/libspoa-dev/usr/lib/x86_64-linux-gnu
> make[1]: Leaving directory '/<>'
>dh_installdocs -O--no-parallel
>dh_installchangelogs -O--no-parallel
>dh_installexamples -O--no-parallel
>dh_installman -O--no-parallel
>dh_installsystemduser -O--no-parallel
>dh_perl -O--no-parallel
>dh_link -O--no-parallel
>dh_strip_nondeterminism -O--no-parallel
>dh_compress -O--no-parallel
>dh_fixperms -O--no-parallel
>dh_missing -O--no-parallel
>dh_dwz -a -O--no-parallel
>dh_strip -a -O--no-parallel
>dh_makeshlibs -a -O--no-parallel
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libspoa7.0.0/DEBIAN/symbols doesn't match 
> completely debian/libspoa7.0.0.symbols.amd64
> --- debian/libspoa7.0.0.symbols.amd64 (libspoa7.0.0_4.0.7+ds-2_amd64)
> +++ dpkg-gensymbols0aC_eE 2022-07-29 09:32:22.859799033 +
> @@ -136,7 +136,7 @@
>   
> _ZNSt5dequeIPKN4spoa5Graph4NodeESaIS4_EE16_M_push_back_auxIJRKS4_EEEvDpOT_@Base
>  4.0.5+ds
>   
> _ZNSt5dequeIPN4spoa5Graph4NodeESaIS3_EE16_M_push_back_auxIJRKS3_EEEvDpOT_@Base
>  4.0.5+ds
>   _ZNSt5dequeIPN4spoa5Graph4NodeESaIS3_EE17_M_reallocate_mapEmb@Base 4.0.5+ds
> - 
> _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE12emplace_backIJRS5_EEEvDpOT_@Base
>  1.1.3
> +#MISSING: 4.0.7+ds-2# 
> _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE12emplace_backIJRS5_EEEvDpOT_@Base
>  1.1.3
>   
> _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
>  1.1.3
>   
> _ZNSt6vectorIPKN4spoa5Graph4NodeESaIS4_EE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPS4_S6_EEmRKS4_@Base
>  4.0.5+ds
>   
> _ZNSt6vectorIPN4spoa5Graph4EdgeESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base
>  4.0.5+ds
> dh_makeshlibs: error: failing due to earlier errors
> make: *** [debian/rules:23: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/spoa_4.0.7+ds-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results

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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that 

Bug#1016602: marked as done (python-mne: vtk[6,7] removal)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 12:34:36 +
with message-id 
and subject line Bug#1016602: fixed in python-mne 1.1.0+dfsg-1
has caused the Debian Bug report #1016602,
regarding python-mne: vtk[6,7] removal
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.)


-- 
1016602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mne
Version: 0.23.4+dfsg-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm
Control: block 1016597 by -1
User: gl...@debian.org
Usertags: vtk6_vtk7_removal

Based on #1013156 and similar bugs:

Dear maintainer,

Debian archive has now three major versions of the VTK (The
Visualization Toolkit) package: vtk6, vtk7 and vtk9. Old vesions
(vtk6 and vtk7) are not supported by upstream and the package itself
is not easy for the mainance.

We aim to drop old and deprecated version vtk6 and vtk7 packages before
the freeze of the Debian 12 Bookworm. Your package depends on vtk6 or
vtk7. Thus we ask you to migrate it to the latest vtk9 package.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: python-mne
Source-Version: 1.1.0+dfsg-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-mne package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 04 Aug 2022 14:10:02 +0200
Source: python-mne
Architecture: source
Version: 1.1.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1016602
Changes:
 python-mne (1.1.0+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
   * Standards-Version: 4.6.1 (routine-update)
   * Set upstream metadata fields: Security-Contact.
   * Switch from python-vtk7 to python-vtk9
 Closes: #1016602
Checksums-Sha1:
 e6c998658b39c527a0a3229dbf6049c82d0ec694 2409 python-mne_1.1.0+dfsg-1.dsc
 f06828a6903907d42dd5fcf142a48c6da24883d7 46773416 
python-mne_1.1.0+dfsg.orig.tar.xz
 f73235fd3765cd5a72ffe1f041ef1868fa1114c5 31860 
python-mne_1.1.0+dfsg-1.debian.tar.xz
 53f53d7c47688408ed582abab4469b198ce07ec6 15891 
python-mne_1.1.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 351d46f19f0211bbfdc5bd0419c5dfd588962c5997c1b0090c6e4a1ac86f69f1 2409 
python-mne_1.1.0+dfsg-1.dsc
 07a143a2880e7d96e729039d05e8d2bd1d23005b9f0e9ada4f94b52327d04ae1 46773416 
python-mne_1.1.0+dfsg.orig.tar.xz
 35b324cc34217a36d06dba6bcbef13e87d0aa88a9bd56155c798432597b5dada 31860 
python-mne_1.1.0+dfsg-1.debian.tar.xz
 193f19cf590efce5f9da9c1bdcb7b116ada10cd12b68e93ad10d229111212096 15891 
python-mne_1.1.0+dfsg-1_amd64.buildinfo
Files:
 7009d7a676ed45e6206a17d2c1f7a1c1 2409 python optional 
python-mne_1.1.0+dfsg-1.dsc
 b48338724601360b0d9dbd9581407c08 46773416 python optional 
python-mne_1.1.0+dfsg.orig.tar.xz
 851658908f03bd0700f78ecbc98977dd 31860 python optional 
python-mne_1.1.0+dfsg-1.debian.tar.xz
 61349d3a1f8fd17cd6836bcf28a04b0f 15891 python optional 
python-mne_1.1.0+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmLrt/QRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtG2OA//ci42l0vcVLWjO/oUGi2aozI/8RjAiYGA
noCC417Cl8a5VMLsRPxbjyWWraGSypfzabhQ5aCVxYcl0xHCzDF8RmAJ00UIINgn
/bWaD04fOX77p8o3YJ9BD1U1yegDcm5zE4gIRULQK9mUFAPW/Pff6QdLRdmAkfmj
0XrY5KQMkw/oOcPt9V9J3xf+lDHKuC41O46DXir/OvSfpxtwFIqTm+bPhlXuX3Qd
mIgezMIB5no8f4HJi/N2Ci1YBWjGHfm7CzockfFUT5Tu4fMyTFeiBybZM6FOje8k
wg1UggoQFjWr6jUBNx948uycgQtF4cao9K7wUmZM7GPTkDe2vk0eup73wnwQgw56
7CNGQ+gsDD/IEaldCodp3rBjW+92RNg0BWZH8MPe1t2LkzDRsvmugL0q9N/RUaIF
hmrRgNgL5lTIr0e9YeN/HYMp+jtz/edSWMbHcTyR3YfhxXTDGQsT/MEDZQcUfZwF
yCrwm7Oc+72MvMz5RkAIU1akAhQQD7gwqwYnzY8xueaHfKlUxmhCkibslwjqQl0n
KqDYnk3gQiL/qQA2sdqMfU43ZxQBU6XmcRDHoX69G+v8pxlL12D2GikU0plq5yPP
qyav+pH//xr4I8KhgXnBQaeuEGN1V5FPsAz9RSjc8CSXKhZlAFtenFy2GK3bNhZs
SAfUTRsQNgw=
=y1+8
-END PGP SIGNATURE End Message ---

Bug#1015994: marked as done (python3-csound depends on python3.9 that will be removed)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 12:34:02 +
with message-id 
and subject line Bug#1015994: fixed in csound 1:6.17.0~dfsg-4
has caused the Debian Bug report #1015994,
regarding python3-csound depends on python3.9 that will be removed
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.)


-- 
1015994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-csound
Version: 1:6.17.0~dfsg-3
Severity: serious

python3-csound depends on python3.9 that will be removed.

A no-change source upload would fix this, but override_dh_python3
forcing a versioned dependency looks bogus and should be dropped.
--- End Message ---
--- Begin Message ---
Source: csound
Source-Version: 1:6.17.0~dfsg-4
Done: IOhannes m zmölnig (Debian/GNU) 

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
csound package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 04 Aug 2022 13:58:11 +0200
Source: csound
Architecture: source
Version: 1:6.17.0~dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 827929 1009185 1015994
Changes:
 csound (1:6.17.0~dfsg-4) unstable; urgency=medium
 .
   [ Dennis Braun ]
   * Bump Standards Version to 4.6.1
 .
   [ IOhannes m zmölnig (Debian/GNU) ]
   * Simplify building with python (Closes: #1015994)
 + Use dh-sequence-python3 instead of '--with=python3'
 + Drop useless variables from python3-csound's Depends/Provides
   * Skip some tests on big-endian.
 Thanks to Graham Inggs  (Closes: #1009185)
   * autopkgtests: Run Python3 tests on all supported py3 versions
   * Disable java packages on hurd and hppa (Closes: #827929)
   * Mark transitional package 'liblua5.1-luacsnd' as "Multi-Arch:same"
   * d/rules:
 + Use execute_after_dh_* rather than override_dh_*
 + Remove config-leftovers on clean
 + Declare that libcsound64-dev is the target package for libcsound64-doc
   * List files that are renamed for arch:any as 'not-installed'
   * Update and modernize lintian-overrides
   * Update d/copyright
 + Add 'Expat' license to d/copyright
 + Add myself to copyright-holders
   * Apply 'wrap-and-sort -ast'
Checksums-Sha1:
 38fb3e598698e670bd84956d2c2cae14c18e4eba 3384 csound_6.17.0~dfsg-4.dsc
 3e791f3e63ea57a7da2d9a10c483400cc1b0e699 43440 
csound_6.17.0~dfsg-4.debian.tar.xz
Checksums-Sha256:
 71710453822b671e43e0d3261ef1fd207af2c7d16b7f17a345d92b8fd674cd9e 3384 
csound_6.17.0~dfsg-4.dsc
 f471bd0190c432bfff65e4568d290d1a8d8df0f558987b507548dbeda251c120 43440 
csound_6.17.0~dfsg-4.debian.tar.xz
Files:
 8fc3fc33f243d812c5c8f93dacdb8a95 3384 sound optional csound_6.17.0~dfsg-4.dsc
 8776512781d013405ea10d10a14addba 43440 sound optional 
csound_6.17.0~dfsg-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmLruR4ACgkQtlAZxH96
NvgXgA/+IFOo+v96w+15Xx3qLlaaVZhACWvVJlhh9E0VIPkrQN5daTvLIRM+HUb6
yaoaglt0e7b2ydHEKXPDdBXrzsd1pXJ7AnyXJcXQ7Gd1cOzZRZ+/zDGkUt45ZwgJ
uyd/ww2rY/ZEKaX/CCyXfQ+HpTI+Wf0fTdXB9/E/ylOv9oSrb3nzdJDVwc+xlRTA
OYHNhSChwUC94lUXEc70oazqmk2ltXrjO4T7ooFckrP+w1OEmfv3x/Q8qGUCJnr3
J3voWD6nCI4r4Q9UbFKXvEdlHOlRVy2ldwSt15zqGLmZOC8WeSug8H8KSvaYAFcJ
2wzuX7EoHyOcEgCzt9/Glb1b5+Jm//W2cqF0ekku5J8T2oJjYfWKCF6+K7xEgdar
1lpvd8LxvXvyfn/L3bEyTnbXxGKfmREfssUQA6LYbfo4+8G40G1r0sUNGPimG85t
pxJMJ2XZF3coLB3+GXjgCB4+alqpHdErBtOpTDXVSbgyJVZkLboa3dyPMJwfBfOJ
nI5M8J7O72+rHan2L+7fZMuoufO/2IXE3iy2jE9xVWrttQ8i3wDLyW2Wb1iiObmU
t6hsL5LXSpLObQdvqBoxpMCak+mlcxv4mVfFpwqoKzfIuR+1sIrOC2K/oV0p3/2Z
lLZMsmwU65hRe8SY30NaP5pF3Ebl1YYN1MkhfpnCnQBT+wCjFF4=
=HSb3
-END PGP SIGNATURE End Message ---

Bug#1013047: marked as done (target-factory: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 12:21:11 +
with message-id 
and subject line Bug#1013047: fixed in target-factory 2.5-1
has caused the Debian Bug report #1013047,
regarding target-factory: ftbfs with GCC-12
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.)


-- 
1013047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:target-factory
Version: 1.4.1-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

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-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/target-factory_1.4.1-1_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
-DGFLAGS_IS_A_DLL=0 -DGLOG_CUSTOM_PREFIX_SUPPORT -Dtarget_factory_EXPORTS 
-I/<>/include -I/<>/obj-x86_64-linux-gnu/src -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -Wall 
-Werror  -Wall -Werror -ggdb -O0 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 
-fno-inline -fPIC -std=gnu++14 -MD -MT 
src/CMakeFiles/target-factory.dir/create_target_v2.cpp.o -MF 
CMakeFiles/target-factory.dir/create_target_v2.cpp.o.d -o 
CMakeFiles/target-factory.dir/create_target_v2.cpp.o -c 
/<>/src/create_target_v2.cpp
[ 75%] Building CXX object src/CMakeFiles/target-factory.dir/error_code.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
-DGFLAGS_IS_A_DLL=0 -DGLOG_CUSTOM_PREFIX_SUPPORT -Dtarget_factory_EXPORTS 
-I/<>/include -I/<>/obj-x86_64-linux-gnu/src -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -Wall 
-Werror  -Wall -Werror -ggdb -O0 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 
-fno-inline -fPIC -std=gnu++14 -MD -MT 
src/CMakeFiles/target-factory.dir/create_target_DPUCVDX8G_ISA1.cpp.o -MF 
CMakeFiles/target-factory.dir/create_target_DPUCVDX8G_ISA1.cpp.o.d -o 
CMakeFiles/target-factory.dir/create_target_DPUCVDX8G_ISA1.cpp.o -c 
/<>/src/create_target_DPUCVDX8G_ISA1.cpp
[ 87%] Building CXX object 
src/CMakeFiles/target-factory.dir/target_factory.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
-DGFLAGS_IS_A_DLL=0 -DGLOG_CUSTOM_PREFIX_SUPPORT -Dtarget_factory_EXPORTS 
-I/<>/include -I/<>/obj-x86_64-linux-gnu/src -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -Wall 
-Werror  -Wall -Werror -ggdb -O0 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 
-fno-inline -fPIC -std=gnu++14 -Wno-unused-variable -MD -MT 
src/CMakeFiles/target-factory.dir/target.pb.cc.o -MF 
CMakeFiles/target-factory.dir/target.pb.cc.o.d -o 
CMakeFiles/target-factory.dir/target.pb.cc.o -c 
/<>/obj-x86_64-linux-gnu/src/target.pb.cc
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
-DGFLAGS_IS_A_DLL=0 -DGLOG_CUSTOM_PREFIX_SUPPORT -Dtarget_factory_EXPORTS 
-I/<>/include -I/<>/obj-x86_64-linux-gnu/src -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -Wall 
-Werror  -Wall -Werror -ggdb -O0 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 
-fno-inline -fPIC -std=gnu++14 -MD -MT 
src/CMakeFiles/target-factory.dir/error_code.cpp.o -MF 
CMakeFiles/target-factory.dir/error_code.cpp.o.d -o 

Bug#1016420: pu bug for reference

[Rene Engelhard]

just for reference: a stable update for this is requested in 
http://bugs.debian.org/1016413

Processed: Bug#1013667 marked as pending in virt-manager

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1013667 [src:virt-manager] virt-manager: FTBFS: tests failed
Added tag(s) pending.

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

Bug#1013667: marked as pending in virt-manager

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #1013667 in virt-manager 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/libvirt-team/virt-manager/-/commit/d246d203204c598341925384a64a9adfecbb2227


d/patches: add fixes from upstream for FTBFS with libvirt 8.5

- tests: Fix with latest osinfo-db
- tests: Fix with latest argcomplete
- tests: Fix with latest libvirt

Closes: #1013667


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013667

Bug#1013667: virt-manager: FTBFS: tests failed

[Fabio Fantoni]

hi, I prepared an MR that fix this: 
https://salsa.debian.org/libvirt-team/virt-manager/-/merge_requests/15




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003165: scikit-learn testing migration

[Andreas Tille]

Hi again,

Am Fri, Jul 29, 2022 at 06:09:26AM +0200 schrieb Andreas Tille:
> I just like to repeat my point:  If the package is to slow on release
> architectures, that we will not manage to fix it, it is in the interest
> of our users to not support the problematic architectures in favour of
> providing it for the architetures where the package is used in practice.
> 
> I have perfectly understood that we will loose several packages on that
> architectures and that this is not a good step.  But having those
> packages not at all is eve worse.

Before we fall into another "do nothing" period:  I will upload
scikit-learn restricted to those architectures only which have all tests
passing and will ask ftpmaster for removal of the others.  If you think
this is a bad idea please give good reasons not to do so or even better
fix the package for the problematic architectures.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#1016281: marked as done (pirs: FTBFS: pirs_diploid.cpp:322:34: error: ‘time’ was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 11:05:25 +
with message-id 
and subject line Bug#1016281: fixed in pirs 2.0.2+dfsg-11
has caused the Debian Bug report #1016281,
regarding pirs: FTBFS: pirs_diploid.cpp:322:34: error: ‘time’ was not declared 
in this scope
to be marked as done.

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

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


-- 
1016281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pirs
Version: 2.0.2+dfsg-10
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I. -I..  -DPKGDATADIR='"/usr/share/pirs"' -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wextra   -fopenmp -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o Profile.o Profile.cpp
> InputStream.h: In constructor ‘InputStream::InputStream(const char*)’:
> InputStream.h:54:23: warning: ‘void* memset(void*, int, size_t)’ clearing an 
> object of non-trivial type ‘class InputStream’; use assignment or 
> value-initialization instead [-Wclass-memaccess]
>54 | memset(this, 0, sizeof(*this));
>   | ~~^~~~
> InputStream.h:25:7: note: ‘class InputStream’ declared here
>25 | class InputStream {
>   |   ^~~
> In file included from pirs_diploid.cpp:12:
> OutputStream.h: In constructor ‘OutputStream::OutputStream()’:
> OutputStream.h:54:23: warning: ‘void* memset(void*, int, size_t)’ clearing an 
> object of non-trivial type ‘class OutputStream’; use assignment or 
> value-initialization instead [-Wclass-memaccess]
>54 | memset(this, 0, sizeof(*this));
>   | ~~^~~~
> OutputStream.h:33:7: note: ‘class OutputStream’ declared here
>33 | class OutputStream {
>   |   ^~~~
> OutputStream.h: In constructor ‘OutputStream::OutputStream(const char*, 
> OutputType)’:
> OutputStream.h:58:23: warning: ‘void* memset(void*, int, size_t)’ clearing an 
> object of non-trivial type ‘class OutputStream’; use assignment or 
> value-initialization instead [-Wclass-memaccess]
>58 | memset(this, 0, sizeof(*this));
>   | ~~^~~~
> OutputStream.h:33:7: note: ‘class OutputStream’ declared here
>33 | class OutputStream {
>   |   ^~~~
> pirs_diploid.cpp: In function ‘void pirs_diploid_parse_command_line(int, 
> char**)’:
> pirs_diploid.cpp:322:34: error: ‘time’ was not declared in this scope
>   322 | seed = (uint64_t)time(NULL) * (uint64_t)getpid();
>   |  ^~~~
> pirs_diploid.cpp:13:1: note: ‘time’ is defined in header ‘’; did you 
> forget to ‘#include ’?
>12 | #include "OutputStream.h"
>   +++ |+#include 
>13 | 
> g++ -DHAVE_CONFIG_H -I. -I..  -DPKGDATADIR='"/usr/share/pirs"' -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wextra   -fopenmp -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o pirs_simulate.o pirs_simulate.cpp
> pirs_simulate.cpp:168:1: warning: invalid suffix on literal; C++11 requires a 
> space between literal and string macro [-Wliteral-suffix]
>   168 | " "DEFAULT_BASE_CALLING_PROFILE"\n"
>   | ^
> pirs_simulate.cpp:174:1: warning: invalid suffix on literal; C++11 requires a 
> space between literal and string macro [-Wliteral-suffix]
>   174 | " "DEFAULT_INDEL_PROFILE"\n"
>   | ^
> pirs_simulate.cpp:180:1: warning: invalid suffix on literal; C++11 requires a 
> space between literal and string macro [-Wliteral-suffix]
>   180 | " "DEFAULT_GC_BIAS_PROFILE_100",\n"
>   | ^
> pirs_simulate.cpp:181:1: warning: invalid suffix on literal; C++11 requires a 
> space between literal and string macro [-Wliteral-suffix]
>   181 | " "DEFAULT_GC_BIAS_PROFILE_150",\n"
>   | ^
> pirs_simulate.cpp:182:1: warning: invalid suffix on literal; C++11 requires a 
> space between literal and string macro [-Wliteral-suffix]
>   182 | " "DEFAULT_GC_BIAS_PROFILE_200",\n"
>   | ^
> pirs_simulate.cpp:672:25: warning: invalid suffix on literal; C++11 requires 
> a space between literal and string macro [-Wliteral-suffix]
>   672 | out_file.printf("%cread_%d_%"PRIu64"/%d\n",
>   | ^
> 

Bug#1015057: marked as done (crust-firmware: FTBFS: collect2: error: ld returned 1 exit status)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 11:04:58 +
with message-id 
and subject line Bug#1015057: fixed in crust-firmware 0.5-2
has caused the Debian Bug report #1015057,
regarding crust-firmware: FTBFS: collect2: error: ld returned 1 exit status
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.)


-- 
1015057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: crust-firmware
Version: 0.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> exec scripts/version.sh /<> build/include/version.h
> exec mkdir -p build/generic_a64/arch/or1k
> exec mkdir -p build/generic_a64/common
> exec mkdir -p build/generic_a64/drivers/clock
> exec mkdir -p build/generic_a64/drivers/css
> exec mkdir -p build/generic_a64/drivers/dram
> exec mkdir -p build/generic_a64/drivers/gpio
> exec mkdir -p build/generic_a64/drivers/irq
> exec mkdir -p build/generic_a64/drivers/msgbox
> exec mkdir -p build/generic_a64/drivers/pmic
> exec mkdir -p build/generic_a64/drivers/regmap
> exec mkdir -p build/generic_a64/drivers/regulator
> exec mkdir -p build/generic_a64/drivers/serial
> exec mkdir -p build/generic_a64/drivers/watchdog
> exec mkdir -p build/generic_a64/lib
> exec or1k-elf-gcc -Ibuild/include -I./platform/"a64"/include 
> -I./arch/"or1k"/include -I./include/common -I./include/lib 
> -I./include/drivers -I./include/stdlib -include config.h -include compiler.h 
> -include kconfig.h -nostdinc -Werror=missing-include-dirs -E -MMD -MT 
> build/generic_a64/arch/or1k/scp.ld.o -P -o 
> build/generic_a64/arch/or1k/scp.ld.o arch/or1k/scp.ld.S
> exec or1k-elf-gcc -Ibuild/include -I./platform/"a64"/include 
> -I./arch/"or1k"/include -I./include/common -I./include/lib 
> -I./include/drivers -I./include/stdlib -include config.h -include compiler.h 
> -include kconfig.h -nostdinc -Werror=missing-include-dirs -Os -pipe -std=c11 
> -fdata-sections -ffunction-sections -fno-builtin -fno-common 
> -fvar-tracking-assignments -ggdb -Wall -Wextra -Wformat=2 -Wpedantic -Wshadow 
> -Werror=implicit-function-declaration -Werror=implicit-int 
> -Werror=pointer-arith -Werror=pointer-sign -Werror=strict-prototypes 
> -Werror=undef -Werror=vla -Wno-missing-field-initializers -ffreestanding 
> -flto -fno-asynchronous-unwind-tables -fno-pie -fomit-frame-pointer 
> -funsigned-char -Werror=implicit-fallthrough=5 -ffixed-r2 -msfimm -mshftimm 
> -msoft-div -msoft-mul -Wa,--fatal-warnings -MMD -c -o 
> build/generic_a64/arch/or1k/counter.o arch/or1k/counter.c
> exec or1k-elf-gcc -Ibuild/include -I./platform/"a64"/include 
> -I./arch/"or1k"/include -I./include/common -I./include/lib 
> -I./include/drivers -I./include/stdlib -include config.h -include compiler.h 
> -include kconfig.h -nostdinc -Werror=missing-include-dirs -Os -pipe -std=c11 
> -fdata-sections -ffunction-sections -fno-builtin -fno-common 
> -fvar-tracking-assignments -ggdb -Wall -Wextra -Wformat=2 -Wpedantic -Wshadow 
> -Werror=implicit-function-declaration -Werror=implicit-int 
> -Werror=pointer-arith -Werror=pointer-sign -Werror=strict-prototypes 
> -Werror=undef -Werror=vla -Wno-missing-field-initializers -ffreestanding 
> -flto -fno-asynchronous-unwind-tables -fno-pie -fomit-frame-pointer 
> -funsigned-char -Werror=implicit-fallthrough=5 -ffixed-r2 -msfimm -mshftimm 
> -msoft-div -msoft-mul -Wa,--fatal-warnings -MMD -c -o 
> build/generic_a64/arch/or1k/exception.o arch/or1k/exception.c
> exec or1k-elf-gcc -Ibuild/include -I./platform/"a64"/include 
> -I./arch/"or1k"/include -I./include/common -I./include/lib 
> -I./include/drivers -I./include/stdlib -include config.h -include compiler.h 
> -include kconfig.h -nostdinc -Werror=missing-include-dirs 
> -Wa,--fatal-warnings -MMD -c -o build/generic_a64/arch/or1k/math.o 
> arch/or1k/math.S
> exec or1k-elf-gcc -Ibuild/include -I./platform/"a64"/include 
> -I./arch/"or1k"/include -I./include/common -I./include/lib 
> -I./include/drivers -I./include/stdlib -include config.h -include compiler.h 
> -include kconfig.h -nostdinc -Werror=missing-include-dirs 
> -Wa,--fatal-warnings -MMD -c -o build/generic_a64/arch/or1k/runtime.o 
> arch/or1k/runtime.S
> exec or1k-elf-gcc -Ibuild/include -I./platform/"a64"/include 
> -I./arch/"or1k"/include -I./include/common -I./include/lib 
> -I./include/drivers -I./include/stdlib -include config.h -include compiler.h 
> 

Bug#1016633: pyhst2: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value'

[Neil Williams]

On Thu, 04 Aug 2022 11:11:37 +0200 Andreas Beckmann 
wrote:
> Source: pyhst2
> Version: 2020c-5

I have looked at the changes for 2022b upstream (sadly, there is no
suitable git tag but the commit I downloaded as a tar.gz was
701a8c1793598a5f4a5d9e0d2b2e0ae89e61). I get the same errors
reported when building that with unstable.

I note that the path reported is c++/10/ and there were issues with
nvidia-cuda-toolkit and g++-11 in other packages. gcc-defaults now
points at g++-12

See 1003037 in astra-toolbox
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003037#24


> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source
> 
> Hi,
> 
> pyhst2 recently started to FTBFS in sid (but not yet in testing):
> 
> /usr/include/c++/10/type_traits:71:52: error: redefinition of
> 'constexpr const _Tp std::integral_constant<_Tp, __v>::value' 71 |
> template |
>^ /usr/include/c++/10/type_traits:59:29: note:
> 'constexpr const _Tp value' previously declared here 59 |
> static constexpr _Tp value = __v; | ^
> 
> Andreas



-- 
Neil Williams
=
https://linux.codehelp.co.uk/


pgpY_pTpAEwTv.pgp
Description: OpenPGP digital signature

Bug#1016363: libx11-6 1.8.1 also breaks glxinfo

[Richard B. Kreckel]

On Wed, 3 Aug 2022 11:33:13 -0700 Max Bell  wrote:
> Why isn't the bug being fixed? That is obviously the correct solution.
So far, they argue that it's correct and only exposed bugs in all those
other packages. Which may even be correct. But without a clear
perspective of getting those fixed anytime soon, it's best to work
around in Debian.

  -richy.
-- 
Richard B. Kreckel

Bug#1016616: marked as done (nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 09:52:15 +
with message-id 
and subject line Bug#1016616: fixed in nvidia-graphics-drivers-legacy-390xx 
390.154-1
has caused the Debian Bug report #1016616,
regarding nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, CVE-2022-31608, 
CVE-2022-31615
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.)


-- 
1016616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5383

CVE-2022-31607  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer (nvidia.ko), where a local user
with basic capabilities can cause improper input validation, which may
lead to denial of service, escalation of privileges, data tampering, and
limited information disclosure.

CVE-2022-31608  NVIDIA GPU Display Driver for Linux contains a
vulnerability in an optional D-Bus configuration file, where a local
user with basic capabilities can impact protected D-Bus endpoints, which
may lead to code execution, denial of service, escalation of privileges,
information disclosure, and data tampering.

CVE-2022-31615  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where a local user with basic
capabilities can cause a null-pointer dereference, which may lead to
denial of service.

Linux Driver Branch CVE IDs Addressed
R515, R510, R470, R450, R390CVE-2022-31607, CVE-2022-31608, CVE-2022-31615


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-390xx
Source-Version: 390.154-1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-legacy-390xx, 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 1016...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-legacy-390xx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 04 Aug 2022 11:32:14 +0200
Source: nvidia-graphics-drivers-legacy-390xx
Architecture: source
Version: 390.154-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1016616
Changes:
 nvidia-graphics-drivers-legacy-390xx (390.154-1) unstable; urgency=medium
 .
   * New upstream legacy branch release 390.154 (2022-08-02).
 * Fixed CVE-2022-31607, CVE-2022-31608, 

Bug#1013929: marked as done (src:goffice: fails to migrate to testing for too long: FTBFS on mips64el)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 09:49:16 +
with message-id 
and subject line Bug#1013929: fixed in goffice 0.10.52-4
has caused the Debian Bug report #1013929,
regarding src:goffice: fails to migrate to testing for too long: FTBFS on 
mips64el
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.)


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

Source: goffice
Version: 0.10.51-1
Severity: serious
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:goffice has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package fails to build from 
source on mips64el where it successfully built in the past.


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


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


I have tagged this bug to only affect sid and bookworm, so it doesn't 
affect (old-)stable.


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: goffice
Source-Version: 0.10.52-4
Done: Dmitry Smirnov 

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated goffice package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 04 Aug 2022 19:23:16 +1000
Source: goffice
Architecture: source
Version: 0.10.52-4
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Closes: 1013929
Changes:
 goffice (0.10.52-4) unstable; urgency=medium
 .
   * Reverted `--without-long-double` on [mips64el] (Closes: #1013929).
 Thanks, Ludovic Rousseau.
Checksums-Sha1:
 3ffa81cee39fa5b131f7c2623f77962bb3d05e3a 2503 goffice_0.10.52-4.dsc
 16290b0a51f3e5b3b925ca7a066ac5e5ef20edf5 23644 goffice_0.10.52-4.debian.tar.xz
 77a337fc630fcecbe7e850b34193590c15ca654b 16889 
goffice_0.10.52-4_amd64.buildinfo
Checksums-Sha256:
 419b92016d86003d4feba184954b72c55b540cb0842dec85578a73d08c3ac4d3 2503 
goffice_0.10.52-4.dsc
 6e2feefef1d9da7284c3f6accf0cc7ef48f01858c07018c780f2ca048bb68a05 23644 
goffice_0.10.52-4.debian.tar.xz
 4bcba67c031165fe266431b10b2bbf368ec244912df6bbc27334d24103317c4d 16889 
goffice_0.10.52-4_amd64.buildinfo
Files:
 5d9833189e2ce0c584e57412f527a49c 2503 libs optional goffice_0.10.52-4.dsc
 3693e61d4e12955bd074c04f0bc47919 23644 libs optional 
goffice_0.10.52-4.debian.tar.xz
 e3514eb3164215302f8a180a82a77ac8 16889 libs optional 
goffice_0.10.52-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAmLrkXUACgkQUra72VOW
jRsWsQ//T0tpXhYveegXQLAo8t/zUfPNudBzPdzLgcOIUTugHBCKaka0f6YVFphb
/JBnuQ3RxsNIP+CBow8iSuRLf8m1lkMMhLeiVSRuY8OQ+9iBJ23Jq5/8sgWyDzjm
9x/zkzwvJfFrlq1uYI0wMxtkW+4D5OIMxlcMhWuyLOD3kfWqKMqJIcE96w0egHSL
+uPAnP3XcMjOofvPMDqG05XGD0kbYjfti1HS4zhI2JX4Y0Z3wwMSKqvNiQG+2lVa
/6KyABgFnxWrZETnaywQHn8137B5Aa4YbSMpJsrqORMo+bSjd7j8j9Y5FDG7LOEZ
7f+vPDnwccYG8FBDJBKFNN3FmhmGxoOv4m/q8CHw6/kXaw5dCNJkWihUDgWg51Mc

Bug#1016223: marked as done (binutils-or1k-elf: FTBFS: stdlib.h:134:10: error: argument 1 is null but the corresponding size argument 3 value is [128, 9223372036854775807] [-Werror=nonnull])

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 09:33:48 +
with message-id 
and subject line Bug#1016223: fixed in binutils-or1k-elf 1.0.6
has caused the Debian Bug report #1016223,
regarding binutils-or1k-elf: FTBFS: stdlib.h:134:10: error: argument 1 is null 
but the corresponding size argument 3 value is [128, 9223372036854775807] 
[-Werror=nonnull]
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.)


-- 
1016223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: binutils-or1k-elf
Version: 1.0.5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I../../src/gas  -I. -I../../src/gas -I../bfd 
> -I../../src/gas/config -I../../src/gas/../include -I../../src/gas/.. 
> -I../../src/gas/../bfd -DLOCALEDIR="\"/usr/share/locale\"" -Wdate-time 
> -D_FORTIFY_SOURCE=2 -W -Wall -Wstrict-prototypes -Wmissing-prototypes 
> -Wshadow -Wstack-usage=262144 -Werror -Wwrite-strings  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o config/obj-elf.o 
> ../../src/gas/config/obj-elf.c
> yes
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) yes
> checking whether the gcc linker (ld -m elf_x86_64) supports shared 
> libraries... yes
> checking dynamic linker characteristics... gcc -DHAVE_CONFIG_H -I. 
> -I../../src/gas  -I. -I../../src/gas -I../bfd -I../../src/gas/config 
> -I../../src/gas/../include -I../../src/gas/.. -I../../src/gas/../bfd 
> -DLOCALEDIR="\"/usr/share/locale\"" -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall 
> -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144 
> -Werror -Wwrite-strings  -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> config/atof-ieee.o ../../src/gas/config/atof-ieee.c
> GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... no
> checking whether to build static libraries... yes
> checking for special C compiler options needed for large files... no
> checking for _FILE_OFFSET_BITS value needed for large files... touch doc/as.1
> perl ../../src/gas/../etc/texi2pod.pl -I "../../src/gas/doc" -I doc -I 
> "../../src/gas/../libiberty" -I "../../src/gas/../bfd/doc" -I ../bfd/doc 
> --no-split -Dman < ../../src/gas/doc/as.texi > doc/as.pod
> no
> checking for aclocal... ${SHELL} '/<>/src/missing' aclocal-1.16
> checking for autoconf... ${SHELL} '/<>/src/missing' autoconf
> checking for autoheader... ${SHELL} '/<>/src/missing' autoheader
> checking whether gcc supports -W... yes
> (pod2man --center="GNU Development Tools" --release="binutils-2.38.90" 
> --section=1 doc/as.pod | \
> sed -e '/^.if n .na/d' > doc/as.1.T$$ && \
> mv -f doc/as.1.T$$ doc/as.1) || \
> (rm -f doc/as.1.T$$ && exit 1)
> checking whether gcc supports -Wall... restore=: && backupdir=".am$$" && \
> rm -rf $backupdir && mkdir $backupdir && \
> if (makeinfo --split-size=500 --split-size=500 --version) >/dev/null 
> 2>&1; then \
>   for f in doc/as.info doc/as.info-[0-9] doc/as.info-[0-9][0-9] doc/as.i[0-9] 
> doc/as.i[0-9][0-9]; do \
> if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
>   done; \
> else :; fi && \
> if makeinfo --split-size=500 --split-size=500 -I "../../src/gas/doc" 
> -I doc -I "../../src/gas/../libiberty" -I "../../src/gas/../bfd/doc" -I 
> ../bfd/doc --no-split  -I doc -I ../../src/gas/doc \
>  -o doc/as.info `test -f 'doc/as.texi' || echo '../../src/gas/'`doc/as.texi; \
> then \
>   rc=0; \
> else \
>   rc=$?; \
>   $restore $backupdir/* `echo "./doc/as.info" | sed 's|[^/]*$||'`; \
> fi; \
> rm -rf $backupdir; exit $rc
> yes
> checking whether gcc supports -Wnarrowing... yes
> checking whether gcc supports -Wwrite-strings... yes
> checking whether gcc supports -Wmissing-format-attribute... yes
> checking whether gcc supports -Wstrict-prototypes... yes
> checking whether gcc supports -Wmissing-prototypes... yes
> checking whether gcc supports -Wold-style-definition... yes
> checking whether gcc supports -pedantic -Wlong-long... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> 

Processed: Bug#1013929 marked as pending in goffice

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1013929 [src:goffice] src:goffice: fails to migrate to testing for too 
long: FTBFS on mips64el
Added tag(s) pending.

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

Bug#1013929: marked as pending in goffice

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #1013929 in goffice 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/debian/goffice/-/commit/43905ed1686ec5cad5f46a22f4ae1ae3e7dec3ff


Revert "Use `--without-long-double` on [mips64el] to fix FTBFS (Closes: 
#1013929)."

This reverts commit 3cd973d85f5b6d337100270e068f09fd30d8cea5.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013929

Bug#1016633: pyhst2: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value'

[Andreas Beckmann]

Source: pyhst2
Version: 2020c-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

pyhst2 recently started to FTBFS in sid (but not yet in testing):

/usr/include/c++/10/type_traits:71:52: error: redefinition of 'constexpr const 
_Tp std::integral_constant<_Tp, __v>::value'
   71 |   template
  |^
   
/usr/include/c++/10/type_traits:59:29: note: 'constexpr const _Tp value' 
previously declared here
   59 |   static constexpr _Tp  value = __v;
  | ^

Andreas


sid.build.gz
Description: application/gzip


testing.build.gz
Description: application/gzip

Bug#1015994: marked as pending in csound

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

Bug #1015994 in csound 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/multimedia-team/csound/-/commit/5e26322a5f40bb89618a4c44805499da8fe7da70


Simplify building with python

Closes: #1015994


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1015994

Processed: Bug#1015994 marked as pending in csound

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1015994 [python3-csound] python3-csound depends on python3.9 that will be 
removed
Added tag(s) pending.

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

Bug#1015998: boost1.74: shlibs don't generate *-py310 dependencies with Python 3.10

[Andreas Beckmann]

On Mon, 25 Jul 2022 03:15:15 +0300 Adrian Bunk  wrote:

Source: boost1.74
Version: 1.74.0-16.1



sed -i -r 's/^(libboost_python([0-9]{2}) \S+ (\S+).*)$$/\1, \3-py\2/' 
debian/libboost-python$(SOVERSION)/DEBIAN/shlibs

...


These {2} should be {3} to work with Python 3.10.


Or probably just '+' to catch all digit counts.
Can't test this right now due to #1016321.

After this got fixed, the rdepends need to be binNMUed:

antimony: antimony
boost1.74: libboost-mpi-python1.74-dev
   libboost-numpy1.74-dev
   libboost-python1.74-dev
calamares: calamares
casacore: libcasa-python3-6 [amd64 arm64 armel armhf i386 mipsel ppc64el s390x]
  libcasa-python3-7 [amd64 arm64 armel armhf i386 mipsel ppc64el s390x]
cctbx: libcctbx0 [amd64 arm64 armel armhf i386 ppc64el s390x]
   python3-cctbx [amd64 arm64 armel armhf i386 ppc64el s390x]
cegui-mk2: python3-libcegui-mk2-0.8.7
ceph: ceph-mgr
ecflow: python3-ecflow
enki-aseba: python3-enki2 [amd64 arm64 i386 mips64el mipsel ppc64el s390x]
esys-particle: esys-particle
freeorion: freeorion
gfal2-bindings: python3-gfal2
glom: glom
  libglom-1.30-0
imath: python3-imath
kig: kig
ledger: ledger
python3-ledger
librcsb-core-wrapper: python3-corepywrap
libtorrent-rasterbar: python3-libtorrent
libvigraimpex: python3-vigra
linuxcnc: linuxcnc-uspace [amd64 arm64 i386 mips64el mipsel ppc64el s390x]
minieigen: python3-minieigen
openstructure: libost-gui2.3 [amd64]
   python3-ost [amd64]
openvdb: python3-openvdb
promod3: python3-promod3 [amd64]
py3exiv2: python3-py3exiv2
pybdsf: python3-bdsf
pycuda/contrib: python3-pycuda [amd64 arm64 ppc64el]
pygattlib: python3-gattlib
pyobjcryst: python3-pyobjcryst [amd64]
pytango: python3-tango
python-casacore: python3-casacore [amd64 arm64 armel armhf i386 mipsel ppc64el 
s390x]
python-demgengeo: python3-gengeo
python-escript: python3-escript [amd64 arm64 armel armhf i386 mipsel ppc64el 
s390x]
python3-escript-mpi [amd64 arm64 armel armhf i386 mipsel 
ppc64el s390x]
python-freecontact: python3-freecontact [amd64 arm64 armhf i386 mips64el mipsel 
ppc64el s390x]
python-mapnik: python3-mapnik
python-pgmagick: python3-pgmagick
pythonmagick: python3-pythonmagick
rdkit: librdkit1
   python3-rdkit
ros-image-common: python3-camera-calibration-parsers
ros-vision-opencv: python3-cv-bridge
tagpy: python3-tagpy
yade: libyade [amd64 arm64 i386 ppc64el s390x]


Andreas

Processed: severity of 943237 is serious

[Debian Bug Tracking System]

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

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

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

Processed: severity of 938644 is serious

[Debian Bug Tracking System]

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

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

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

Bug#1016321: boost1.74: FTBFS: runtime error: file /<>/tools/boostbook/xsl/annotation.xsl line 432 element element xsl:element: The effective name '' is not a valid QName.

[Andreas Beckmann]

There is also this error earlier in the logfile:

error: Problems running latex. Check your installation or look for typos 
in _formulas.tex and check _formulas.log!



Andreas

Bug#1016090: python-django breaks lots of autopkgtests

[James Bennett]


> 
> On Aug 1, 2022, at 12:33 PM, Chris Lamb  wrote:
> Hmpf, this is deeply unfortunate. I was working under the incorrect
> belief that the 4.0.x series was now the LTS branch. A number of
> things encouraged this interpretation, including that the 4.0.x and
> 4.1.x were the release streams that were receiving security and
> targeted bugfix releases, and this was happening as a relatively
> consistent pair. (As in, not the 3.x stream.)

To clarify: the LTS is always the third and final (X.2) release of a major 
version. So 3.2 is the current LTS; the next LTS will be 4.2, then 5.2, etc.

At this stage in the cycle:

* 4.1 receives full support for bugs of most levels of severity.
* 4.0 receives only fixes for security and data-loss bugs, and will become 
unsupported once 4.2 is released, expected April 2023.
* 3.2 LTS receives only fixes for security and data-loss bugs, and will become 
unsupported in April 2024, approximately 30 months after its initial release.

Bug#1016450: marked as done (gdcm: autopkgtest failure on s390x)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 06:54:04 +
with message-id 
and subject line Bug#1016450: fixed in gdcm 3.0.13-3
has caused the Debian Bug report #1016450,
regarding gdcm: autopkgtest failure on s390x
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.)


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

Source: gdcm
Version: 3.0.13-2
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package gdcm, great. However, 
it fails on s390x. Currently this failure is blocking the migration to 
testing [1]. Can you please investigate the situation and fix it? Please 
be aware that s390x is big-endian and the only be architecture we run 
autopkgtests for.


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

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=gdcm

https://ci.debian.net/data/autopkgtest/testing/s390x/g/gdcm/23826805/log.gz

Running Tests
PASS
MediaStorage is 1.2.840.10008.5.1.4.1.1.6.1 [Ultrasound Image Storage]
TransferSyntax is 1.2.840.10008.1.2 [Implicit VR Little Endian: Default 
Transfer Syntax for DICOM]
gdcminfo: ./Source/MediaStorageAndFileFormat/gdcmLookupTable.cxx:173: 
virtual void 
gdcm::LookupTable::SetLUT(gdcm::LookupTable::LookupTableType, const 
unsigned char*, unsigned int): Assertion 
`Internal->Length[type]*(BitSample/8) == length' failed.
/tmp/autopkgtest-lxc.q54akkws/downtmp/build.vE1/src/debian/tests/run-unit-test: 
line 26:  6180 Aborted gdcminfo gdcm-US-ALOKA-16.dcm

autopkgtest [10:00:10]: test run-unit-test



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gdcm
Source-Version: 3.0.13-3
Done: Mathieu Malaterre 

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated gdcm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Aug 2022 08:29:13 +0200
Source: gdcm
Architecture: source
Version: 3.0.13-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Mathieu Malaterre 
Closes: 1016331 1016450
Changes:
 gdcm (3.0.13-3) unstable; urgency=medium
 .
   [ Mohammed Bilal ]
   * change test data
   * Fix autopkgtest for s390 (Closes: #1016450)
 .
   [ Mathieu Malaterre ]
   * Team upload.
   * d/patches: Fix doxygen/pdf generation. Closes: #1016331
Checksums-Sha1:
 9e70b04a1b8f9034a9bf267d6e0d1a260cab0edf 3910 gdcm_3.0.13-3.dsc
 26ccdaab3603cf381e6cbea016fe584f53add981 278832 gdcm_3.0.13-3.debian.tar.xz
 8cf831a02734489cbcaca3491119d71e562b8739 34718 gdcm_3.0.13-3_source.buildinfo
Checksums-Sha256:
 d3944f1b3c8c8b124f28c785143fcb33c526c66ea863f09950cc00eaf6e379d3 3910 
gdcm_3.0.13-3.dsc
 f80d002ce74f4c2f0a50ef12e32f5d39d572f4c81ed0c17dbca00591b46b90f6 278832 
gdcm_3.0.13-3.debian.tar.xz
 b311255ae94355965589ec12e6ba4678f77b99793203b23bb1438d6a6ee076e4 34718 
gdcm_3.0.13-3_source.buildinfo
Files:
 f551b6e3e61dd0389e673a2f387ba27c 3910 libs optional gdcm_3.0.13-3.dsc
 af7a0118f86ff50d1959236450cf3e8a 278832 libs optional 
gdcm_3.0.13-3.debian.tar.xz
 02e49cb7fd75a15f024772d07749db59 34718 libs optional 
gdcm_3.0.13-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmLrZ3IRHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0X4oA/9HwEQZMEq/UnqcpPtzaRI9TrCJaHqT+xK
BH8wSjI2IWvoGtb2TAqLnkOwthlrNwlrnEamk/NmNs0E425xYk/ua1FiOmNlt/7k
prv0Y96P5RNE6Jj24akUuW5e0jxNmhQdVwDz8gmh61c11oooucpDmrY+C8qnZdbp
Pkm/U6hN3iUAU+xBtS7J+BP5RHdaXWfXTIRFdNAUNoHO5wbb8xN18rBAR8p2mt0j
5OrtlekwkS9bxP52BlxtcuZBNnR8i9YfzzZ9oBzsj0kHWRq2ZhX7CiaSclRkSgmJ
xalYAbZqJ/CoJSS0BP6h07+MfXSqLc0eHiE3N/+QW9qfVeT4KvsJrsnuAQ/Z6Cpz

Bug#1016363: marked as done (libx11 v1.8.1 does fail in a subtle way withj modale dialogs)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 06:54:28 +
with message-id 
and subject line Bug#1016363: fixed in libx11 2:1.8.1-2
has caused the Debian Bug report #1016363,
regarding libx11 v1.8.1 does fail in a subtle way withj modale dialogs
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.)


-- 
1016363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libx11-6
Version: 2:1.8.1-1
Severity: critical

When upgrading libx11 from 2:1.7.5-1 to 2:1.8.1-1 X will fail in a very
strange way immediately when a modal dialog starts (like pinentry).

I use fvwm and have focus follow mouse. When pinentry starts, the focus
still stays on the window that I use before. (xterm) But there is no way
anymore to change focus. Even more, when killing the pinentry, the
process is gone but the window is still on the screen. The whole X is
fully infunctional afterwards.

The only solution is to kill (-9) the whole X stack. A simple kill
(-TERM) will not end the dysfunctional X session.

Going back to libx11 2:1.7.5-1 solves the problem.

Note, the same bug happens on gentoo. I opened bug #862115 over there
yesterday.

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

Kernel: Linux 5.16.17 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libx11-6 depends on:
ii  libc62.33-8
ii  libx11-data  2:1.7.5-1
ii  libxcb1  1.14-3

libx11-6 recommends no packages.

libx11-6 suggests no packages.

-- no debconf information

-- 
Klaus Ethgen   http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libx11
Source-Version: 2:1.8.1-2
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated libx11 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Aug 2022 09:21:33 +0300
Source: libx11
Built-For-Profiles: noudeb
Architecture: source
Version: 2:1.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 1016363
Changes:
 libx11 (2:1.8.1-2) unstable; urgency=medium
 .
   * rules: Disable thread safety constructor. (Closes: #1016363)
Checksums-Sha1:
 593f59d7aa1bc8c97ec487283555466f6099fcd1 2542 libx11_1.8.1-2.dsc
 bb98578b574e31553d40d4157517396116a9c8bd 101135 libx11_1.8.1-2.diff.gz
 c62eb49d9bc38218dffeaf60d1559ac1f685d255 7284 libx11_1.8.1-2_source.buildinfo
Checksums-Sha256:
 2a64edad1d57a373ed6f6d27749c4ff75c9fd6c593e0c01ab1f8ca1f54f235a7 2542 
libx11_1.8.1-2.dsc
 c5e6e957daef88c03ab95d5a93d870e40c9e1bed56d63ed9f686547eecdee694 101135 
libx11_1.8.1-2.diff.gz
 f2a2bd0c98223fbfc45cbd96216487c4a5526a1a85c4408cb260a7c417dda2ba 7284 
libx11_1.8.1-2_source.buildinfo
Files:
 29f594f582d6915e395a59ddfda8a3ab 2542 x11 optional libx11_1.8.1-2.dsc
 bf94b0cfc1a9eb8dde1ca8b0709e8e96 101135 x11 optional libx11_1.8.1-2.diff.gz
 389447f0f987396b385144f1677e4ae7 7284 x11 optional 
libx11_1.8.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmLraNkACgkQy3AxZaiJ
hNzagA//STb25yJyM2PTgU/P4PZQS2A/Ph1sz+eJtPniETLUoS6+S9hnk6Q0TqnQ
ck2q8Gz4B4FyZapFaEHhZ/F5YYiaKe78hsAtHheOn6hxtebbzvnc84xa84Csxy81
Sw0eWW3nHaoMupaQPdH/bVgEU3bVWAEZgSkm1qStEezhwjX9WxdSad452aZSLJir
t59/uO/hlM8GaYOVa3t/DohdKPe+zgBZhJ7PRIjJT9RDlMS2lMHhyyDio6MfIIE7
lBuGqt8idblEPBjcIRdg4N9Ulh8Wak9VOYgj8TiBI7TnyN6R5G1Lv3k/pXZomTZk
fM34PwWVS4JP1Fc0WfvT+3k7l45pMzELNhAyQqawCY1QraQOIrsS4afRtOtz+QPT

Bug#1016331: marked as done (gdcm: FTBFS: make[2]: *** [Makefile:12: refman.pdf] Error 1)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 06:54:04 +
with message-id 
and subject line Bug#1016331: fixed in gdcm 3.0.13-3
has caused the Debian Bug report #1016331,
regarding gdcm: FTBFS: make[2]: *** [Makefile:12: refman.pdf] Error 1
to be marked as done.

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

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


-- 
1016331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdcm
Version: 3.0.13-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory 
> '/<>/obj-x86_64-linux-gnu/Utilities/doxygen/latex'
> rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl 
> refman.pdf
> pdflatex refman
> This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> (./refman.tex
> LaTeX2e <2022-06-01> patch level 5
> L3 programming layer <2022-07-15>
> make[2]: *** [Makefile:12: refman.pdf] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/gdcm_3.0.13-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results

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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: gdcm
Source-Version: 3.0.13-3
Done: Mathieu Malaterre 

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated gdcm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Aug 2022 08:29:13 +0200
Source: gdcm
Architecture: source
Version: 3.0.13-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Mathieu Malaterre 
Closes: 1016331 1016450
Changes:
 gdcm (3.0.13-3) unstable; urgency=medium
 .
   [ Mohammed Bilal ]
   * change test data
   * Fix autopkgtest for s390 (Closes: #1016450)
 .
   [ Mathieu Malaterre ]
   * Team upload.
   * d/patches: Fix doxygen/pdf generation. Closes: #1016331
Checksums-Sha1:
 9e70b04a1b8f9034a9bf267d6e0d1a260cab0edf 3910 gdcm_3.0.13-3.dsc
 26ccdaab3603cf381e6cbea016fe584f53add981 278832 gdcm_3.0.13-3.debian.tar.xz
 8cf831a02734489cbcaca3491119d71e562b8739 34718 gdcm_3.0.13-3_source.buildinfo
Checksums-Sha256:
 d3944f1b3c8c8b124f28c785143fcb33c526c66ea863f09950cc00eaf6e379d3 3910 
gdcm_3.0.13-3.dsc
 f80d002ce74f4c2f0a50ef12e32f5d39d572f4c81ed0c17dbca00591b46b90f6 278832 
gdcm_3.0.13-3.debian.tar.xz
 b311255ae94355965589ec12e6ba4678f77b99793203b23bb1438d6a6ee076e4 34718 
gdcm_3.0.13-3_source.buildinfo
Files:
 f551b6e3e61dd0389e673a2f387ba27c 3910 libs optional gdcm_3.0.13-3.dsc
 af7a0118f86ff50d1959236450cf3e8a 278832 libs optional 
gdcm_3.0.13-3.debian.tar.xz
 02e49cb7fd75a15f024772d07749db59 34718 libs optional 
gdcm_3.0.13-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmLrZ3IRHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0X4oA/9HwEQZMEq/UnqcpPtzaRI9TrCJaHqT+xK
BH8wSjI2IWvoGtb2TAqLnkOwthlrNwlrnEamk/NmNs0E425xYk/ua1FiOmNlt/7k
prv0Y96P5RNE6Jj24akUuW5e0jxNmhQdVwDz8gmh61c11oooucpDmrY+C8qnZdbp
Pkm/U6hN3iUAU+xBtS7J+BP5RHdaXWfXTIRFdNAUNoHO5wbb8xN18rBAR8p2mt0j
5OrtlekwkS9bxP52BlxtcuZBNnR8i9YfzzZ9oBzsj0kHWRq2ZhX7CiaSclRkSgmJ

Bug#1016269: marked as done (smlsharp: FTBFS: configure: error: Specify --with-incompatible-llvm if you really want to build SML# with it.)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 06:55:16 +
with message-id 
and subject line Bug#1016269: fixed in smlsharp 4.0.0+git20211227.5af5945b-2
has caused the Debian Bug report #1016269,
regarding smlsharp: FTBFS: configure: error: Specify --with-incompatible-llvm 
if you really want to build SML# with it.
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.)


-- 
1016269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: smlsharp
Version: 4.0.0+git20211227.5af5945b-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> checking for opt... /usr/lib/llvm-14/bin/opt
> checking for llvm-dis... /usr/lib/llvm-14/bin/llvm-dis
> checking for llvm-as... /usr/lib/llvm-14/bin/llvm-as
> checking for LLVM compatibility... no
> configure: WARNING: SML# does not support LLVM 14.0. Build may fail due to 
> incompatibility.
> configure: error: Specify --with-incompatible-llvm if you really want to 
> build SML# with it.
> make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 1
> make[1]: Leaving directory '/<>'


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/smlsharp_4.0.0+git20211227.5af5945b-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results

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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: smlsharp
Source-Version: 4.0.0+git20211227.5af5945b-2
Done: Nobuhiro Iwamatsu 

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

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated smlsharp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 04 Aug 2022 15:19:35 +0900
Source: smlsharp
Architecture: source
Version: 4.0.0+git20211227.5af5945b-2
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu 
Changed-By: Nobuhiro Iwamatsu 
Closes: 1016269
Changes:
 smlsharp (4.0.0+git20211227.5af5945b-2) unstable; urgency=medium
 .
   * Fix build with LLVM 14.0 (Closes: #1016269)
 Add d/patches/0001-Add-support-LLVM-14.0.patch.
Checksums-Sha1:
 7501cde73078dc8c9b9ade5ab6d4ab332532c060 2019 
smlsharp_4.0.0+git20211227.5af5945b-2.dsc
 71078fad242fe69d1d75af8c902f0379cd332e9a 6328 
smlsharp_4.0.0+git20211227.5af5945b-2.debian.tar.xz
 bb5f1fc1b1d0f801ebe8fe3deec0b9cd38151c00 8273 
smlsharp_4.0.0+git20211227.5af5945b-2_amd64.buildinfo
Checksums-Sha256:
 3b201b4bbea637d2244c465906d6412fbfe088f682f383356ddfba8a919c3442 2019 
smlsharp_4.0.0+git20211227.5af5945b-2.dsc
 01eb01a3eb9ca02a12b8fe2377b8f5933555a93cc284ab57cf6e63bc61b61670 6328 
smlsharp_4.0.0+git20211227.5af5945b-2.debian.tar.xz
 e5f05d1a8e5ea914ef0e302e1a38697ff8f199d8d64e09b747f642dda1ab1c0a 8273 
smlsharp_4.0.0+git20211227.5af5945b-2_amd64.buildinfo
Files:
 79ae6ba6a60a422c3f0d3e7c178857ad 2019 devel optional 
smlsharp_4.0.0+git20211227.5af5945b-2.dsc
 382d5c5e7a337e7b02b3608c1766794f 6328 devel optional 
smlsharp_4.0.0+git20211227.5af5945b-2.debian.tar.xz
 6a606d596fbacb7e553416c97d30ac74 8273 devel optional 
smlsharp_4.0.0+git20211227.5af5945b-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAmLraDEACgkQMiR/u0Ct

Bug#1016331: marked as pending in gdcm

[Mathieu Malaterre]

Control: tag -1 pending

Hello,

Bug #1016331 in gdcm 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/gdcm/-/commit/03bc56ee308df00a816be236a634aba5ec98783d


d/patches: Fix doxygen/pdf generation. Closes: #1016331


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1016331

Processed: Bug#1016331 marked as pending in gdcm

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1016331 [src:gdcm] gdcm: FTBFS: make[2]: *** [Makefile:12: refman.pdf] 
Error 1
Added tag(s) pending.

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

Bug#1016250: marked as done (parsinsert: FTBFS: ParsInsert.cpp:420:17: error: ‘time’ was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Thu, 04 Aug 2022 06:22:13 +
with message-id 
and subject line Bug#1016250: fixed in parsinsert 1.04-12
has caused the Debian Bug report #1016250,
regarding parsinsert: FTBFS: ParsInsert.cpp:420:17: error: ‘time’ was not 
declared in this scope
to be marked as done.

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

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


-- 
1016250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: parsinsert
Version: 1.04-11
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o ParsInsert.o ParsInsert.cpp
> ParsInsert.cpp:411:45: warning: macro "__DATE__" might prevent reproducible 
> builds [-Wdate-time]
>   411 | DisplayL("%s\nCommand Line:[%s]\n", VERSION, cmd.c_str());
>   | ^~~
> ParsInsert.cpp:56:82: warning: macro "__TIME__" might prevent reproducible 
> builds [-Wdate-time]
>56 | #define VERSION APPNAME " 
> Version 1.04 " __DATE__ " " __TIME__
>   |   
>^~~~
> ParsInsert.cpp:411:45: note: in expansion of macro ‘VERSION’
>   411 | DisplayL("%s\nCommand Line:[%s]\n", VERSION, cmd.c_str());
>   | ^~~
> ParsInsert.cpp:416:25: warning: macro "__DATE__" might prevent reproducible 
> builds [-Wdate-time]
>   416 | DisplayT(USAGE, VERSION, APPNAME);
>   | ^~~
> ParsInsert.cpp:56:82: warning: macro "__TIME__" might prevent reproducible 
> builds [-Wdate-time]
>56 | #define VERSION APPNAME " 
> Version 1.04 " __DATE__ " " __TIME__
>   |   
>^~~~
> ParsInsert.cpp:416:25: note: in expansion of macro ‘VERSION’
>   416 | DisplayT(USAGE, VERSION, APPNAME);
>   | ^~~
> In file included from PNode.h:31,
>  from PNode.cpp:27:
> ParsimonySet.h: In member function ‘void CParsimonySet::TraceSegments(const 
> char*)’:
> ParsimonySet.h:429:22: warning: ISO C++ forbids converting a string constant 
> to ‘char*’ [-Wwrite-strings]
>   429 | DisplayL("%s [", label);
>   |  ^~
> ParsimonySet.h:431:26: warning: ISO C++ forbids converting a string constant 
> to ‘char*’ [-Wwrite-strings]
>   431 | DisplayL(" %3d", segCounts[k]);
>   |  ^~
> ParsimonySet.h:432:22: warning: ISO C++ forbids converting a string constant 
> to ‘char*’ [-Wwrite-strings]
>   432 | DisplayL("]\n");
>   |  ^
> AttrList.cpp: In member function ‘int CAttrList::AddHex(const char*, long 
> unsigned int)’:
> AttrList.cpp:173:28: warning: format ‘%X’ expects argument of type ‘unsigned 
> int’, but argument 3 has type ‘long unsigned int’ [-Wformat=]
>   173 | sprintf(buf, "0x%08X", value);
>   | ~~~^   ~
>   ||   |
>   ||   long unsigned int
>   |unsigned int
>   | %08lX
> In file included from ParsInsert.h:29,
>  from ParsInsert.cpp:34:
> ParsimonySet.h: In member function ‘void CParsimonySet::TraceSegments(const 
> char*)’:
> ParsimonySet.h:429:22: warning: ISO C++ forbids converting a string constant 
> to ‘char*’ [-Wwrite-strings]
>   429 | DisplayL("%s [", label);
>   |  ^~
> ParsimonySet.h:431:26: warning: ISO C++ forbids converting a string constant 
> to ‘char*’ [-Wwrite-strings]
>   431 | DisplayL(" %3d", segCounts[k]);
>   |  ^~
> ParsimonySet.h:432:22: warning: ISO C++ forbids converting a string constant 
> to ‘char*’ [-Wwrite-strings]
>   432 | DisplayL("]\n");
>   |  ^
> PNode.cpp: In member function ‘void CPTree::Parse(const char*)’:
> PNode.cpp:299:42: warning: ISO C++ forbids converting a string constant to 
> ‘char*’ [-Wwrite-strings]
>   299 |