Processed: firmware-carl9170: undeclared file conflict with firmware-linux-free

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + firmware-linux-free
Bug #1050989 [firmware-carl9170] firmware-carl9170: undeclared file conflict 
with firmware-linux-free
Added indication that 1050989 affects firmware-linux-free

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

Bug#1050989: firmware-carl9170: undeclared file conflict with firmware-linux-free

[Helmut Grohne]

Package: firmware-carl9170
Version: 1.9.9-399-gcd480b9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + firmware-linux-free

firmware-carl9170 installs /lib/firmware/carl9170-1.fw, which is also
currently installed by firmware-linux-free. I see that this is quite
intentional as this piece of firmware is being split out from the larger
firmware package. On a packaging level, this needs to be addressed with
Replaces, Conflicts or diversions. Failing to do so, results in an
unpack error from dpkg. I understand that getting the firmware removed
from firmware-linux-free may take a bit and you can only then set up the
correct Breaks+Replaces. That's fine. Just keep this bug open until that
matter is resolved.

Helmut

Bug#1050973: marked as done (lastpass-cli: Please update to 1.3.5 upstream to fix certificate error)

[Debian Bug Tracking System]

Your message dated Fri, 01 Sep 2023 00:04:26 +
with message-id 
and subject line Bug#1050973: fixed in lastpass-cli 1.3.5-1
has caused the Debian Bug report #1050973,
regarding lastpass-cli: Please update to 1.3.5 upstream to fix certificate error
to be marked as done.

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

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


-- 
1050973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lastpass-cli
Version: 1.3.4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

With the current version of the package, 1.3.4, lpass is broken due to an 
upstream certificate change. This has been addressed in the 1.3.5 release:

https://github.com/lastpass/lastpass-cli/issues/653

Please update to the 1.3.5 upstream release.

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(100, 'focal-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.90.1-microsoft-standard-WSL2 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
--- End Message ---
--- Begin Message ---
Source: lastpass-cli
Source-Version: 1.3.5-1
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated lastpass-cli 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, 31 Aug 2023 16:37:52 -0700
Source: lastpass-cli
Architecture: source
Version: 1.3.5-1
Distribution: unstable
Urgency: medium
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Closes: 1050973
Changes:
 lastpass-cli (1.3.5-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #1050973)
Checksums-Sha1:
 871edba0c05ee6d8f00023dab91aa0c1808b48c5 2041 lastpass-cli_1.3.5-1.dsc
 234f2f673c82f8a89ffab299e40bac1d6089c69e 117250 lastpass-cli_1.3.5.orig.tar.gz
 9a092cd02e45e9f1867ca74ed577ac0f13dfe065 6548 
lastpass-cli_1.3.5-1.debian.tar.xz
 1369da02f89c32afa4e61b51b0b120bb749d0d58 7688 
lastpass-cli_1.3.5-1_amd64.buildinfo
Checksums-Sha256:
 7885e3edc0b00e98d077acb0e4a5b1e1552e353b4fcd42e85036b781faca124d 2041 
lastpass-cli_1.3.5-1.dsc
 2681d6305b39f610aa4e93017e43b78a5a2a9408b0c9798a9ea7ee8f2e2878c4 117250 
lastpass-cli_1.3.5.orig.tar.gz
 fcb3be18c0c5e45e5c2323528408c92de10e7705cb4eac4a4da66ed1093e6b0c 6548 
lastpass-cli_1.3.5-1.debian.tar.xz
 9ecc2d987ae03e56ad85dd4c20d055f30c3a93923c73ef0a87ff170a2a1bfdb3 7688 
lastpass-cli_1.3.5-1_amd64.buildinfo
Files:
 4a93f82e5bbdebe79e5f520b70b0eb78 2041 utils optional lastpass-cli_1.3.5-1.dsc
 de607f9fc436c81b1db34c9261b6f1d5 117250 utils optional 
lastpass-cli_1.3.5.orig.tar.gz
 3a97eb399bb97f54e0eab17cff21497d 6548 utils optional 
lastpass-cli_1.3.5-1.debian.tar.xz
 0a4c40ef24f0dbbadb4789638406fe43 7688 utils optional 
lastpass-cli_1.3.5-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAmTxKJsACgkQHpU+J9Qx
Hlhoxg/+Kw91tNhbhFglJ/ZBRBiIGH3bsOsWGhrYZmci4M3H3B44ZgVOSfO0K2Ri
hP5xibUznLM2g14DEs7/vhckGsBJygObU+EIQRNqxW90gIEQRIlPuC/JmxGf6FD+
5C9RZe2lP4+04HW2P6/LLlgRscfGN5iKc4fw0ETwvjv/eDZCN27qlpELd1Sb7XW5
I0oW6I1wOUTT9qHwtmnQZWgdTt8IO2DzgjFa3Vf3tmPI8fGd36HpyX5btKU/hZ6X
AGde5U3Ln+rwsLwFrJYioy6zPdF/RZgztN37lXCaIQE+z2lVgeNE2P7INcV46UxS
6uSdxXhprFNMsOm9XFMqGJiylOkk7w4q8pF27gyRYqOA2De8XLcxxxtEKihRQEwT
oRxcKyidfZKGjD5ugXs6196loZNAQlGRSR0xFA1/bEiEkPGPaVGNyfC1h+8SBX5A
ENgngvi3b0nTUj/qem6nZKScuMtXOobQanRCyUh/33mIrBCQaHH4MpyzDPWb87Ep

Processed: Re: lastpass-cli: Please update to 1.3.5 upstream to fix certificate error

[Debian Bug Tracking System]

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

> tags 1050973 + pending
Bug #1050973 [lastpass-cli] lastpass-cli: Please update to 1.3.5 upstream to 
fix certificate error
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1050973: lastpass-cli: Please update to 1.3.5 upstream to fix certificate error

[Chris Lamb]

tags 1050973 + pending
thanks


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#1050436: upower: autopkgtest regression on i386: excessive precision?

[Michael Biebl]

On Thu, 24 Aug 2023 17:18:35 +0200 Paul Gevers  wrote:

Source: upower 1.90.2-4
Severity: serious
Tags: sid trixie
X-Debbugs-CC: b...@debian.org
User: debian...@lists.debian.org
Usertags: regression
Control: affects -1 src:libgudev

Dear maintainer(s),

With a recent upload of upower, the autopkgtest of upower fails on i386 
in testing when that autopkgtest is run with the binary packages of 
upower and libgudev from unstable. It passes when run with only packages 
from testing. In tabular form:


passfail
libgudev   from testing238-2
upower from testing1.90.2-4
all others from testingfrom testing

I copied some of the output at the bottom of this report. Looking at the 
error this *seems* to me the result of the excessive precision of i386, 
but I hope the i386 porter (in XDCC) can shed his light on that too.


Currently this regression is blocking the migration of libgudev to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

https://ci.debian.net/data/autopkgtest/testing/i386/u/upower/37102682/log.gz

208s ==
208s FAIL: test_battery_energy_charge_mixed 
(__main__.Tests.test_battery_energy_charge_mixed)

208s battery which reports both current charge and energy
208s --
208s Traceback (most recent call last):
208s   File "/usr/libexec/upower/integration-test.py", line 887, in 
test_battery_energy_charge_mixed
208s self.assertEqual(self.get_dbus_dev_property(bat0_up, 
'Percentage'), 40.0)

208s AssertionError: 40.01 != 40.0


Adrian, as i386 porter, could you have a look at this?


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1050973: lastpass-cli: Please update to 1.3.5 upstream to fix certificate error

[Alex Ford]

Package: lastpass-cli
Version: 1.3.4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

With the current version of the package, 1.3.4, lpass is broken due to an 
upstream certificate change. This has been addressed in the 1.3.5 release:

https://github.com/lastpass/lastpass-cli/issues/653

Please update to the 1.3.5 upstream release.

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(100, 'focal-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.90.1-microsoft-standard-WSL2 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Bug#1050891: sccache - update for new addr2line.

[Peter Michael Green]

On 31/08/2023 08:50, Jonas Smedegaard wrote:


, but it is a risky game,


Letting stuff  fall ever more out of date is also a risky game as
it tends to mean stuff gets even more intertwined when we
do finally try to update it and if the version of rust-cargo used
by debcargo gets too far out of date then things can get
*really* painful.



We do have the option of using semver-suffix packages, but
we try to use those sparingly for several reasons.

* Debian in general discourages multiple copies of what is
  essentially the same codebase.
* It's more packages to maintain (or fail to maintain)
* The packages need to pass NEW, which introduces unpredictable
   delay to the whole process.

It's worth noting that most languages in Debian don't normally
put any upper limits on dependencies used at build time,
despite having far less ability to detect problems at compile
time than rust does.

I'm not at all convinced that these dependency bumps are any
riskier than many uploads for packages in other languages that
happen, unnoticed, all the time.


Allow those responsible for maintaining packages to actually do that.
Please in future coordinate *before* doing breaking changes (unless it
happens accidentally, of course).


How exactly do you want this coordination to work? how long
do you think it is reasonable for us to give you to respond? how
should the actual uploads be handled given that ideally for
minimum breakage the packages would be uploaded at the
same time?

Processed: severity of 1042984 is important

[Debian Bug Tracking System]

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

> severity 1042984 important
Bug #1042984 [src:golang-1.19] golang-1.19 should not be in trixie
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1050952: marked as done (r-bioc-rhdf5lib: autopkgtest regression: Expected '1.10.8', got '1.10.10')

[Debian Bug Tracking System]

Your message dated Thu, 31 Aug 2023 19:05:27 +
with message-id 
and subject line Bug#1050952: fixed in r-bioc-rhdf5lib 1.22.0+dfsg-2
has caused the Debian Bug report #1050952,
regarding r-bioc-rhdf5lib: autopkgtest regression: Expected '1.10.8', got 
'1.10.10'
to be marked as done.

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

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


-- 
1050952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-rhdf5lib
Version: 1.6.3+dfsg-1
Severity: serious
Justification: Test regression

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

See 
https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-bioc-rhdf5lib/37206202/log.gz.

> 69s - FAILED[data]: test_library_version.R<3--3>
> 69s  call| expect_identical(libver, "1.10.8")
> 69s  diff| Expected '1.10.8', got '1.10.10'

Please fix the testcases so that they won't fail each time the HDF5
release number is bumped.

Thanks in advance,
_g.

- -- System Information:
Debian Release: 11.7
Architecture: amd64 (x86_64)

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAmTw1b4ACgkQ7+hsbH/+
z4MVFAf/cmL8/oW3owSvrnYpqf68EwqR4stYB/NS+KOqtM/B5Ed2FYoUkxmgOhWG
9q9u1lkW0T0mMVlVMLKJlhKdfS/brQgk/Z+LYmc5sqTpvj5Re2C2DIW/XhyAsNxn
Nz7HiRURg4MOKd2F9Nq5iRoI8mVwgtiRiTI12Fne5QlAyXMBOGD4IBrgINOttiKT
LPkZgaO+jXN7nV9HOYkeFm2Jf8bRVEpS5t1ityuN+HVohl0YJ8ieqwzQFsKnAave
o1ag7xZ21iX6hF88ApfTlzBc6SdkRPBf0/AjNuAWnBz0UQHbYVSsKYtL1TshnPUN
virmPFskzmAa345AD6/BA/gyzMME6g==
=UnqI
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: r-bioc-rhdf5lib
Source-Version: 1.22.0+dfsg-2
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-bioc-rhdf5lib 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, 31 Aug 2023 20:39:35 +0200
Source: r-bioc-rhdf5lib
Architecture: source
Version: 1.22.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1050952
Changes:
 r-bioc-rhdf5lib (1.22.0+dfsg-2) unstable; urgency=medium
 .
   * Do not fail test for any mikro version 1.10.x of hdflib
 Closes: #1050952
Checksums-Sha1:
 a4fd95f14f58b6ce40bbe028d851cec005c6f40f 2120 r-bioc-rhdf5lib_1.22.0+dfsg-2.dsc
 50d045bc6945404fce652015072ad48cb03b8977 7676 
r-bioc-rhdf5lib_1.22.0+dfsg-2.debian.tar.xz
 295a7aba4070813afee96f6c13d1c4c92491e941 11404 
r-bioc-rhdf5lib_1.22.0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 eed25b8178cc6ba1d0a4ebc1e5c542d421785c680ce85d4190b416a0b0ab2d35 2120 
r-bioc-rhdf5lib_1.22.0+dfsg-2.dsc
 bfd6cd584b2f339752ad9c0c39b8b95cef19122c98d1cc37487838b0ccec1d52 7676 
r-bioc-rhdf5lib_1.22.0+dfsg-2.debian.tar.xz
 e342cd35e7c068eb1f713739b6a567cedd63923866b0e092ba92c138c4326563 11404 
r-bioc-rhdf5lib_1.22.0+dfsg-2_amd64.buildinfo
Files:
 53c94a6697776ca6c7378fb49d31fcd9 2120 gnu-r optional 
r-bioc-rhdf5lib_1.22.0+dfsg-2.dsc
 4a6b7d8f1ff028d2518019fc34156385 7676 gnu-r optional 
r-bioc-rhdf5lib_1.22.0+dfsg-2.debian.tar.xz
 35e44ee591da372eebf0b379ad4044a2 11404 gnu-r optional 
r-bioc-rhdf5lib_1.22.0+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmTw4JwRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEIXw//Vy6wBzCUALvXBbvYkiFASxF+PPD5SFim
w1Gjbm0a+ay4+BtLTAG4kAF+heN6GFJxWLuHQQJQdLWDOH836jokGeSa0KkMi2DF
OoHQVVPKWluhjv3OpALDRR4YvdHoNGFJAfv9RVXbkStoxzNe/JNH2YbtzGWm3gO7
RJrtn5kUiflDLHEELz2RoV2uzdV8cw8sDYKO4wGkKCaCXhZC0ht2LDJGygi2TZOT
1xANkQfTGUqS6yjD/SuF28C9I4hyuM6ucVVvu6h80hhGGQ6oFxeyPmNdq48aVkB3
KZ+XKgbZ41/oC45uZnePAD6sgl/NggmyNaizUyrVqmGUK6zLXyJn2ftJ4S5AJpVZ

Bug#1050952: r-bioc-rhdf5lib: autopkgtest regression: Expected '1.10.8', got '1.10.10'

[Gilles Filippini]

Source: r-bioc-rhdf5lib
Version: 1.6.3+dfsg-1
Severity: serious
Justification: Test regression

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

See 
https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-bioc-rhdf5lib/37206202/log.gz.

> 69s - FAILED[data]: test_library_version.R<3--3>
> 69s  call| expect_identical(libver, "1.10.8")
> 69s  diff| Expected '1.10.8', got '1.10.10'

Please fix the testcases so that they won't fail each time the HDF5
release number is bumped.

Thanks in advance,
_g.

- -- System Information:
Debian Release: 11.7
Architecture: amd64 (x86_64)

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAmTw1b4ACgkQ7+hsbH/+
z4MVFAf/cmL8/oW3owSvrnYpqf68EwqR4stYB/NS+KOqtM/B5Ed2FYoUkxmgOhWG
9q9u1lkW0T0mMVlVMLKJlhKdfS/brQgk/Z+LYmc5sqTpvj5Re2C2DIW/XhyAsNxn
Nz7HiRURg4MOKd2F9Nq5iRoI8mVwgtiRiTI12Fne5QlAyXMBOGD4IBrgINOttiKT
LPkZgaO+jXN7nV9HOYkeFm2Jf8bRVEpS5t1ityuN+HVohl0YJ8ieqwzQFsKnAave
o1ag7xZ21iX6hF88ApfTlzBc6SdkRPBf0/AjNuAWnBz0UQHbYVSsKYtL1TshnPUN
virmPFskzmAa345AD6/BA/gyzMME6g==
=UnqI
-END PGP SIGNATURE-

Bug#1037579: marked as done (armnn: ftbfs with GCC-13 on arm64 and armhf)

[Debian Bug Tracking System]

Your message dated Thu, 31 Aug 2023 18:00:11 +
with message-id 
and subject line Bug#1037579: fixed in armnn 23.08-2
has caused the Debian Bug report #1037579,
regarding armnn: ftbfs with GCC-13 on arm64 and armhf
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.)


-- 
1037579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:armnn
Version: 20.08-12
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/armnn_20.08-12_unstable_gccexp.log
The last lines of the build log are at the end of this report.

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

[...]
[ 25%] Building CXX object 
src/backends/reference/workloads/CMakeFiles/armnnRefBackendWorkloads.dir/RefReshapeWorkload.cpp.o
cd /<>/build-area/src/backends/reference/workloads && /usr/bin/c++ 
-DARMNN_DYNAMIC_BACKEND_ENABLED -DARMNN_SERIALIZER 
-DARMNN_SERIALIZER_SCHEMA_PATH=\"/<>/src/armnnSerializer/ArmnnSchema.fbs\"
 -DARMNN_TF_LITE_PARSER -DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LIB 
-DDYNAMIC_BACKEND_BUILD_DIR=\"/<>/build-area\" 
-I/<>/include -I/<>/profiling 
-I/<>/src/armnn -I/<>/src/armnnUtils 
-I/<>/src/backends -I/<>/src/profiling 
-I/<>/profiling/common/include -isystem 
/<>/third-party -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++14 -Wall -Wextra -Werror -Wold-style-cast 
-Wno-missing-braces -Wconversion -Wsign-conversion -fPIC   
'-DDYNAMIC_BACKEND_PATHS="/usr/lib/x86_64-linux-gnu/armnn22/"' -MD -MT 
src/backends/reference/workloads/CMakeFiles/armnnRefBackendWorkloads.dir/Ref
 ReshapeWorkload.cpp.o -MF 
CMakeFiles/armnnRefBackendWorkloads.dir/RefReshapeWorkload.cpp.o.d -o 
CMakeFiles/armnnRefBackendWorkloads.dir/RefReshapeWorkload.cpp.o -c 
/<>/src/backends/reference/workloads/RefReshapeWorkload.cpp
[ 26%] Building CXX object 
src/backends/reference/workloads/CMakeFiles/armnnRefBackendWorkloads.dir/RefResizeBilinearWorkload.cpp.o
cd /<>/build-area/src/backends/reference/workloads && /usr/bin/c++ 
-DARMNN_DYNAMIC_BACKEND_ENABLED -DARMNN_SERIALIZER 
-DARMNN_SERIALIZER_SCHEMA_PATH=\"/<>/src/armnnSerializer/ArmnnSchema.fbs\"
 -DARMNN_TF_LITE_PARSER -DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LIB 
-DDYNAMIC_BACKEND_BUILD_DIR=\"/<>/build-area\" 
-I/<>/include -I/<>/profiling 
-I/<>/src/armnn -I/<>/src/armnnUtils 
-I/<>/src/backends -I/<>/src/profiling 
-I/<>/profiling/common/include -isystem 
/<>/third-party -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++14 -Wall -Wextra -Werror -Wold-style-cast 
-Wno-missing-braces -Wconversion -Wsign-conversion -fPIC   
'-DDYNAMIC_BACKEND_PATHS="/usr/lib/x86_64-linux-gnu/armnn22/"' -MD -MT 
src/backends/reference/workloads/CMakeFiles/armnnRefBackendWorkloads.dir/Ref
 ResizeBilinearWorkload.cpp.o -MF 
CMakeFiles/armnnRefBackendWorkloads.dir/RefResizeBilinearWorkload.cpp.o.d -o 
CMakeFiles/armnnRefBackendWorkloads.dir/RefResizeBilinearWorkload.cpp.o -c 
/<>/src/backends/reference/workloads/RefResizeBilinearWorkload.cpp
[ 26%] Building CXX object 
src/backends/backendsCommon/CMakeFiles/armnnBackendsCommon.dir/MemCopyWorkload.cpp.o
cd /<>/build-area/src/backends/backendsCommon && /usr/bin/c++ 
-DARMNN_DYNAMIC_BACKEND_ENABLED -DARMNN_SERIALIZER 
-DARMNN_SERIALIZER_SCHEMA_PATH=\"/<>/src/armnnSerializer/ArmnnSchema.fbs\"
 -DARMNN_TF_LITE_PARSER -DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LIB 
-DDYNAMIC_BACKEND_BUILD_DIR=\"/<>/build-area\" 
-I/<>/include -I/<>/profiling 

Bug#1042942: marked as done (armnn: FTBFS on i386 due to test failures)

[Debian Bug Tracking System]

Your message dated Thu, 31 Aug 2023 18:00:11 +
with message-id 
and subject line Bug#1042942: fixed in armnn 23.08-2
has caused the Debian Bug report #1042942,
regarding armnn: FTBFS on i386 due to test failures
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.)


-- 
1042942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:armnn
Version: 20.08-13
Severity: serious

armnn 20.08-13 seems to compile correctly on i386, but then FTBFS due to
the following test failures:

Running 430 test cases...
./src/armnn/test/ModelAccuracyCheckerTest.cpp(103):  [1;31;49merror: in 
"ModelAccuracyCheckerTest/TestFloat32OutputTensorAccuracy": check totalAccuracy 
== 33.321f has failed [0;39;49m
./src/armnn/test/ModelAccuracyCheckerTest.cpp(107):  [1;31;49merror: in 
"ModelAccuracyCheckerTest/TestFloat32OutputTensorAccuracy": check totalAccuracy 
== 66.641f has failed [0;39;49m
./src/armnn/test/optimizations/ConvertConstantsBFloatTests.cpp(120):  
[1;31;49merror: in "Optimizer/ConvertConstantsBFloatToFloatTest": check data[3] 
== 3.1072295E29f has failed [0;39;49m
./src/armnn/test/optimizations/ConvertConstantsBFloatTests.cpp(121):  
[1;31;49merror: in "Optimizer/ConvertConstantsBFloatToFloatTest": check data[4] 
== 9.131327E-10f has failed [0;39;49m
./src/armnn/test/optimizations/ConvertConstantsBFloatTests.cpp(123):  
[1;31;49merror: in "Optimizer/ConvertConstantsBFloatToFloatTest": check data[6] 
== -3.1072295E29f has failed [0;39;49m
./src/armnn/test/optimizations/ConvertConstantsBFloatTests.cpp(124):  
[1;31;49merror: in "Optimizer/ConvertConstantsBFloatToFloatTest": check data[7] 
== -9.131327E-10f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1366):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counter->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1408):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWUnits->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1436):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWoDevice->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1490):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWDevice->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1519):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWoCounterSet->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1561):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWNumberOfCores->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1600):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWMultiCoreDevice->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1648):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWMultiCoreDeviceWParentCategory->m_Multiplier == 123.45f has failed 
[0;39;49m
./src/profiling/test/ProfilingTests.cpp(1684):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWCounterSet->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1708):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
counterWDeviceWCounterSet->m_Multiplier == 123.45f has failed [0;39;49m
./src/profiling/test/ProfilingTests.cpp(1741):  [1;31;49merror: in 
"ExternalProfiling/CheckCounterDirectoryRegisterCounter": check 
anotherCounter->m_Multiplier == .00043f has failed [0;39;49m

 [1;31;49m*** 17 failures are detected in the test module "UnitTests"
 [0;39;49mmake[1]: *** [debian/rules:67: override_dh_auto_test] Error 201
make[1]: Leaving directory '/<>'
make: *** [debian/rules:30: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


Full build logs at:
https://buildd.debian.org/status/fetch.php?pkg=armnn=i386=20.08-13=1690924863=0
--- End Message ---
--- Begin Message ---
Source: armnn
Source-Version: 23.08-2
Done: Emanuele Rocca 

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

A summary of the changes 

Bug#1043333: marked as done (python3-sugar3: Recommends unavailable package 'telepathy-salut')

[Debian Bug Tracking System]

Your message dated Thu, 31 Aug 2023 17:34:52 +
with message-id 
and subject line Bug#104: fixed in sugar-toolkit-gtk3 0.120-2
has caused the Debian Bug report #104,
regarding python3-sugar3: Recommends unavailable package 'telepathy-salut'
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.)


-- 
104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-sugar3
Version: 0.120-1
Severity: serious
Justification: Policy 2.2.1

Dear Maintainer,

python3-sugar3 Recommens the binary package "telepathy-salut".
However, "telepathy-salut" has been removed in 2022-12 from both
unstable and testing (bookworm, thus now stable).
See bug [938645]

Since this is contradition with the debian policy [2.2.1], would
you be so kind and remove the offending "Recommends" line?

cheers

[938645] https://bugs.debian.org/938645
[2.2.1] 
https://www.debian.org/doc/debian-policy/ch-archive.html#the-main-archive-area
--- End Message ---
--- Begin Message ---
Source: sugar-toolkit-gtk3
Source-Version: 0.120-2
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated sugar-toolkit-gtk3 
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, 31 Aug 2023 19:07:22 +0200
Source: sugar-toolkit-gtk3
Architecture: source
Version: 0.120-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Sugar Team 
Changed-By: Jonas Smedegaard 
Closes: 104
Changes:
 sugar-toolkit-gtk3 (0.120-2) unstable; urgency=medium
 .
   * stop recommend telepathy-salut;
 closes: bug#104, thanks to IOhannes m zmölnig
Checksums-Sha1:
 7da03c698e392ccd21351ea90f07cf0341ba88d7 2648 sugar-toolkit-gtk3_0.120-2.dsc
 dfc9c972ec1959c4e1c223b474851e7b9281802a 15428 
sugar-toolkit-gtk3_0.120-2.debian.tar.xz
 a5dc8ec865317b19b3ab3e7eed3dc040b59dc2f6 16729 
sugar-toolkit-gtk3_0.120-2_amd64.buildinfo
Checksums-Sha256:
 308b0e663e7f4c28bfbbde091c28ea27250320cd3bac5b50abc0c82c74796f66 2648 
sugar-toolkit-gtk3_0.120-2.dsc
 f2d16ee0a440e1bfeb2a412497788a9517ff3fa96df07da1a06fd98582af13b3 15428 
sugar-toolkit-gtk3_0.120-2.debian.tar.xz
 a709dd009e7e697536a7f3036624d51d37fd98811892f4a1bb7eaa55c3cb9d84 16729 
sugar-toolkit-gtk3_0.120-2_amd64.buildinfo
Files:
 16b40fdf8e34325b89af935b357a147c 2648 python optional 
sugar-toolkit-gtk3_0.120-2.dsc
 63f391b9611cd60ef7547a3394538839 15428 python optional 
sugar-toolkit-gtk3_0.120-2.debian.tar.xz
 9ba2b9c22e3678a9df8cb16f9a56d79d 16729 python optional 
sugar-toolkit-gtk3_0.120-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTwyZsACgkQLHwxRsGg
ASGxSw/+KMvblEQ0dD/fP3nRJqRDv4PTAuhuCLKDsPB8x/k7up6K1qdt9JQy7D5q
4BjwxoGYFry0CapOAYUvhu6w5TiKGxAKpb8eK+FiAVIliKUfE0U7VgNSQeajWbD8
hIF3P3+FP1GAi5rp+aQImeOMiGfuFL9K/8BjcwW6COf/GtvUvczYOZ96LdXZk7Tc
zUcEjB0eHsDLFOEh9tP7aKn+/vneBhPTpSXh9QriIm8quS/9giRFagEwhqsAdkal
nROPSrmkBl0NvHGismU/NMKkmyRDfytaHlzTaYMR8phAg3B4w607yg96WufG9NVU
SWwoRGcXJTnGUMMRPU+HMRNI7h09RNaMHGugJ85ibQJPE993h4kL8+h+yH5z+qWM
Q25RDCjsimmoOxVpbpU24fD1Ug/ZxrIqrsfadUVxIrHhjysj1jU617l/T6UbAvF9
cMp+FaGQdYY+hRfz4mewPu9RJVkkveoZdea6lU99LUNnjPqZ/dtCeeoRBlEAigDl
KIwpnuRq8hR5v7X5ftAOItRNp0ASA4GDDKbtjkur35xrrklQIk/Cy6tkpOgBhUvX
1omfXeoUt5XgczCLKcNtAh31Cqz96/cqXZmrqZevnZAuiBEVt1qTLRBcvFwntw2z
3AIQGxqqLXokkqFeZMEHPrFWMejTsYlcjvbD+O0bkmNjnXybRq0=
=4RKf
-END PGP SIGNATURE End Message ---

Bug#1050946: openbox-gnome-session: missing dependencies, not all RequiredComponents exist any more

[Simon McVittie]

Package: openbox-gnome-session
Version: 3.6.1-11
Severity: grave
Justification: renders package unusable

To reproduce


* Start from a basic non-GUI virtual machine (I used autopkgtest-build-qemu)
* Ensure that a user account exists
* # apt install lightdm xorg openbox-gnome-session
* # reboot
* Log in as the user account, selecting "GNOME/Openbox" from the menu of
  possible X11 sessions

Expected result
===

A basic GNOME-Flashback-like session with Openbox as window manager

Actual result
=

Aug 31 16:55:58 host gnome-session-binary[1795]: WARNING: Unable to find 
required component 'org.gnome.SettingsDaemon.A11ySettings'
...
Aug 31 16:55:58 host gnome-session-binary[1795]: WARNING: Unable to find 
required component 'org.gnome.SettingsDaemon.XSettings'
Aug 31 16:55:58 host gnome-session-binary[1795]: WARNING: Unable to find 
required component 'gnome-panel'
Aug 31 16:55:58 host gnome-session-binary[1795]: WARNING: Unable to find 
required component 'nautilus-classic'
Aug 31 16:55:58 host gnome-session-binary[1795]: WARNING: Unable to find 
required component 'gnome-flashback-services'

and the session fails with the GNOME Session "something went wrong"
full-screen dialog.

Root cause
==

/usr/share/gnome-session/sessions/openbox-gnome.session declares the
following as required components of a GNOME/Openbox session:

openbox;
org.gnome.SettingsDaemon.A11ySettings;
[some more pieces of gnome-settings-daemon]
org.gnome.SettingsDaemon.XSettings;
gnome-panel;
nautilus-classic;
gnome-flashback-services

but openbox-gnome-session does not have Depends or even Recommends on the
necessary packages to provide those components.

As a minimum, I think it needs to depend on gnome-settings-daemon,
gnome-panel and gnome-flashback, but I tried installing those packages
and that did not fix the failure to start.

gnome-settings-daemon no longer has Clipboard or Mouse plugins according
to gnome-flashback commits

and
.

nautilus-classic hasn't existed for 5
years according to gnome-flashback commit
.

I don't know what gnome-flashback-services is/was, but
gnome-session-flashback lists gnome-flashback as a required component
instead.

Thanks,
smcv

Processed: Re: Bug#1042911: Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open load file: No such file or directory, assoc

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1016558
Bug #1042911 [elpa-muse] Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: 
Cannot open load file: No such file or directory, assoc
1042911 was not blocked by any bugs.
1042911 was not blocking any bugs.
Added blocking bug(s) of 1042911: 1016558

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

Bug#1042911: Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open load file: No such file or directory, assoc

[Nicholas D Steeves]

Control: block -1 by 1016558

Hi,

I'm just updating this bug to note the adopted muse-el package is just
about ready to upload (the ITA is also a pseudo-RFS bug), and I plan to
upload in the next few days.  If this update isn't enough to prevent
autoremoval...well, at least the package will be fixed very soon.

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#1050943: bladerf accesses the Internet during package build

[Benjamin Drung]

Package: bladerf
Version: 0.2023.02-1
Severity: serious
Tags: patch
Justification: Policy 4.9
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
X-Debbugs-Cc: bdr...@debian.org

Dear Maintainer,

bladerf 0.2023.02-1 fails to build from source on Ubuntu, because it
tries to access the Internet (see Debian policy 4.9):

```
python3 -m build --sdist --outdir=debian/tmp/ 
host/libraries/libbladeRF_bindings/python
* Creating venv isolated environment...
* Installing packages in isolated environment... (setuptools >= 40.8.0, wheel)
WARNING: The directory '/sbuild-nonexistent/.cache/pip' or its parent directory 
is not owned or is not writable by the current user. The cache has been 
disabled. Check the permissions and owner of that directory. If executing pip 
with sudo, you should use sudo's -H flag.
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 
'NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known')': /simple/wheel/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 
'NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known')': /simple/wheel/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 
'NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known')': /simple/wheel/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 
'NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known')': /simple/wheel/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 
'NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known')': /simple/wheel/
ERROR: Could not find a version that satisfies the requirement wheel (from 
versions: none)
ERROR: No matching distribution found for wheel

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/build/__main__.py", line 375, in main
built = build_call(
^^^
  File "/usr/lib/python3/dist-packages/build/__main__.py", line 208, in 
build_package
out = _build(isolation, builder, outdir, distribution, config_settings, 
skip_dependency_check)
  

  File "/usr/lib/python3/dist-packages/build/__main__.py", line 145, in _build
return _build_in_isolated_env(builder, outdir, distribution, 
config_settings)
   
^^
  File "/usr/lib/python3/dist-packages/build/__main__.py", line 113, in 
_build_in_isolated_env
env.install(builder.build_system_requires)
  File "/usr/lib/python3/dist-packages/build/env.py", line 214, in install
_subprocess(cmd)
  File "/usr/lib/python3/dist-packages/build/env.py", line 79, in _subprocess
raise e
  File "/usr/lib/python3/dist-packages/build/env.py", line 76, in _subprocess
subprocess.run(cmd, check=True, stdout=subprocess.PIPE, 
stderr=subprocess.STDOUT)
  File "/usr/lib/python3.11/subprocess.py", line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/tmp/build-env-c4ez2a0s/bin/python', 
'-Im', 'pip', 'install', '--use-pep517', '--no-warn-script-location', '-r', 
'/tmp/build-reqs-kxypfyca.txt']' returned non-zero exit status 1.

ERROR Command '['/tmp/build-env-c4ez2a0s/bin/python', '-Im', 'pip', 'install', 
'--use-pep517', '--no-warn-script-location', '-r', 
'/tmp/build-reqs-kxypfyca.txt']' returned non-zero exit status 1.
```

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

  * Use pybuild for building the Python3 bindings to avoid Internet access
(LP: #2033661)


Thanks for considering the patch.

-- 
Benjamin Drung
Debian & Ubuntu Developer
diff -Nru bladerf-0.2023.02/debian/control bladerf-0.2023.02/debian/control
--- bladerf-0.2023.02/debian/control2023-07-12 17:45:05.0 +0200
+++ bladerf-0.2023.02/debian/control2023-08-31 16:21:33.0 +0200
@@ -15,10 +15,8 @@
libusb2-dev [kfreebsd-any],
   pandoc [!kfreebsd-any],
pkg-config,
-  python3-build,
python3-dev,
-  python3-setuptools,
-  python3-venv
+  python3-setuptools
 Standards-Version: 4.6.2
 Rules-Requires-Root: no
 Section: comm
@@ -94,7 +92,7 @@
 Architecture: any
 Multi-Arch: foreign
 Depends: libbladerf-dev (= ${binary:Version}),
- python3, python3-cffi, ${python3:Depends},
+ python3-cffi, ${python3:Depends},
  ${misc:Depends}
 Description: Nuand bladeRF software-defined radio device (Python)

Bug#1050942: FTBFS: Failed 1/1 test programs. 5/246 subtests failed.

[Joao Eriberto Mota Filho]

Package: blhc
Version: 0.13-5
Severity: serious
Tags: ftbfs upstream
Justification: fails to build from source
X-Debbugs-Cc: eribe...@debian.org, Simon Ruderich 

Dear Simon Ruderich,

Currently blhc fails to build from source in Debian Sid. This issue was
detected in Salsa[1].

[1] https://salsa.debian.org/debian/blhc/-/jobs/4635438

I also tested it in a fresh jail:

dh_auto_test
/usr/bin/perl Build test --verbose 1

#   Failed test './t/logs/arch-avr32 --color (output)'
#   at t/tests.t line 45.
#  got: 'Use of uninitialized value $os in pattern match (m//) at 
./bin/blhc line 1194.
# Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 
1198.
# Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 
1202.
# LDFLAGS missing (-Wl,-z,relro): gcc -o test test.o
# CFLAGS missing (-fstack-protector-strong): gcc -D_FORTIFY_SOURCE=2 -g -O2 
-Wformat -Wformat-security -Werror=format-security -Wall -c test.c
# LDFLAGS missing (-Wl,-z,relro): gcc -o test test.o
# '
# expected: 'CFLAGS missing (-fstack-protector-strong): gcc 
-D_FORTIFY_SOURCE=2 -g -O2 -Wformat -Wformat-security -Werror=format-security 
-Wall -c test.c
# '

#   Failed test './t/logs/arch-avr32 (output)'
#   at t/tests.t line 45.
#  got: 'Use of uninitialized value $os in pattern match (m//) at 
./bin/blhc line 1194.
# Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 
1198.
# Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 
1202.

[...]

# checking './t/logs/debian-hardening-wrapper'...
# HARDENING WRAPPER: no checks possible, aborting
# '

#   Failed test './t/logs/arch-i386 ./t/logs/arch-amd64 ./t/logs/arch-avr32 
./t/logs/ignore-flag --ignore-arch-flag i386:-fstack-protector-strong 
--ignore-arch-flag mipsel:-Werror=format-security (output)'
#   at t/tests.t line 45.
#  got: 'Use of uninitialized value $os in pattern match (m//) at 
./bin/blhc line 1194.
# Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 
1198.
# Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 
1202.

[...]

# CFLAGS missing (-O2): gcc -g -fstack-protector-strong -Wformat 
-Wformat-security -Werror=format-security -D_FORTIFY_SOURCE=2 -c test-c.c
# '

#   Failed test './t/logs/arch-i386 ./t/logs/arch-amd64 ./t/logs/arch-avr32 
./t/logs/ignore-line --ignore-arch-line "i386:gcc .+ -fPIE .+" 
--ignore-arch-line "mipsel:gcc .+ -Wl,-z,relro -Wl,-z,now .+" (output)'
#   at t/tests.t line 45.
#  got: 'Use of uninitialized value $os in pattern match (m//) at 
./bin/blhc line 1194.
# Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 
1198.
# Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 
1202.

[...]


# Looks like you failed 5 tests of 246.
t/tests.t ..
1..246
[...]
not ok 14 - ./t/logs/arch-avr32 --color (output)
[...]
not ok 164 - ./t/logs/arch-avr32 (output)
[...]
not ok 242 - ./t/logs/bad-ldflags ./t/logs/empty ./t/logs/arch-avr32 
./t/logs/debian-hardening-wrapper (output)
[...]
not ok 244 - ./t/logs/arch-i386 ./t/logs/arch-amd64 ./t/logs/arch-avr32 
./t/logs/ignore-flag --ignore-arch-flag i386:-fstack-protector-strong 
--ignore-arch-flag mipsel:-Werror=format-security (output)
[...]
not ok 246 - ./t/logs/arch-i386 ./t/logs/arch-amd64 ./t/logs/arch-avr32 
./t/logs/ignore-line --ignore-arch-line "i386:gcc .+ -fPIE .+" 
--ignore-arch-line "mipsel:gcc .+ -Wl,-z,relro -Wl,-z,now .+" (output)
Dubious, test returned 5 (wstat 1280, 0x500)
Failed 5/246 subtests 

Test Summary Report
---
t/tests.t (Wstat: 1280 (exited 5) Tests: 246 Failed: 5)
  Failed tests:  14, 164, 242, 244, 246
  Non-zero exit status: 5
Files=1, Tests=246,  3 wallclock secs ( 0.02 usr  0.00 sys +  2.46 cusr  0.37 
csys =  2.85 CPU)
Result: FAIL
Failed 1/1 test programs. 5/246 subtests failed.


Regards,

Eriberto

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

Kernel: Linux 6.1.0-11-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8), LANGUAGE=C.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages blhc depends on:
ii  libdpkg-perl  1.22.0

blhc recommends no packages.

blhc suggests no packages.

-- debconf-show failed

Bug#1050937: protobuf: FTBFS: ModuleNotFoundError: No module named 'tzdata'

[Bo YU]

Source: protobuf
Version: 3.21.12-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

protobuf fails to build from source. From my build log on amd64:

```
Traceback (most recent call last):
  File "/usr/lib/python3.11/zoneinfo/_common.py", line 12, in load_tzdata
return resources.files(package_name).joinpath(resource_name).open("rb")
   ^
  File "/usr/lib/python3.11/importlib/resources/_common.py", line 22, in files
return from_package(get_package(package))

  File "/usr/lib/python3.11/importlib/resources/_common.py", line 53, in 
get_package
resolved = resolve(package)
   
  File "/usr/lib/python3.11/importlib/resources/_common.py", line 44, in resolve
return cand if isinstance(cand, types.ModuleType) else 
importlib.import_module(cand)
   
^
  File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "", line 1204, in _gcd_import
  File "", line 1176, in _find_and_load
  File "", line 1126, in _find_and_load_unlocked
  File "", line 241, in _call_with_frames_removed
  File "", line 1204, in _gcd_import
  File "", line 1176, in _find_and_load
  File "", line 1140, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'tzdata'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/<>/python3/setup.py", line 324, in 
setup(
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in 
setup
return distutils.core.setup(**attrs)
   ^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
185, in setup
return run_commands(dist)
   ^^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
201, in run_commands
dist.run_commands()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
969, in run_commands
self.run_command(cmd)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 223, 
in run
self.run_tests()
  File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 226, 
in run_tests
test = unittest.main(
   ^^
  File "/usr/lib/python3.11/unittest/main.py", line 101, in __init__
self.parseArgs(argv)
  File "/usr/lib/python3.11/unittest/main.py", line 150, in parseArgs
self.createTests()
  File "/usr/lib/python3.11/unittest/main.py", line 161, in createTests
self.test = self.testLoader.loadTestsFromNames(self.testNames,
^^
  File "/usr/lib/python3.11/unittest/loader.py", line 220, in loadTestsFromNames
suites = [self.loadTestsFromName(name, module) for name in names]
 
  File "/usr/lib/python3.11/unittest/loader.py", line 220, in 
suites = [self.loadTestsFromName(name, module) for name in names]
  
  File "/usr/lib/python3.11/unittest/loader.py", line 191, in loadTestsFromName
return self.loadTestsFromModule(obj)
   ^
  File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 57, in 
loadTestsFromModule
tests.append(self.loadTestsFromName(submodule))
 ^
  File "/usr/lib/python3.11/unittest/loader.py", line 154, in loadTestsFromName
module = __import__(module_name)
 ^^^
  File 
"/<>/python3/google/protobuf/internal/well_known_types_test.py", 
line 56, in 
_TZ_JAPAN = zoneinfo.ZoneInfo('Japan')
^^
  File "/usr/lib/python3.11/zoneinfo/_common.py", line 24, in load_tzdata
raise ZoneInfoNotFoundError(f"No time zone found with key {key}")
zoneinfo._common.ZoneInfoNotFoundError: 'No time zone found with key Japan'
make[1]: *** [debian/rules:105: override_dh_auto_test-arch] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:23: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
```

The full log you can get from riscv64 builder also:
https://buildd.debian.org/status/fetch.php?pkg=protobuf=riscv64=3.21.12-6%2Bb1=1693418596=0

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1050350: marked as done (flycheck: keep flycheck out of testing until it finds an uploader)

[Debian Bug Tracking System]

Your message dated Thu, 31 Aug 2023 14:34:30 +
with message-id 
and subject line Bug#1050404: fixed in flycheck 33~git20230824.e56e30d-1
has caused the Debian Bug report #1050404,
regarding flycheck: keep flycheck out of testing until it finds an uploader
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.)


-- 
1050404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flycheck
Severity: serious
Justification: Team decision
X-Debbugs-Cc: debian-emac...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Nobody has stepped up to take care of flycheck, and it currently
blocks the transition of emacs 29 to testing. 

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

Kernel: Linux 6.3.0-1-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmTmA08ACgkQA0U5G1Wq
FSFx4RAAug0/SVS+L2nFAKwRHgsqypfuSZ46JP+ayMV+O3yLc2vyZy6HOgt1Ew7c
Psfjt3s3ba2adbOZraPT0CAx2Dgz/0cKg2Rm4M6fMOCwYsqjwNSlPpE8rw0o0k5i
xPV5x+WKpoGWQB4sWW3QqDmZEdU3OY3szkpCKxDnR2Dk4rGRXBbI1utH4DOpdT8R
fCN6Qg+MWtimK+M33n/nklxvK8Ze7RLo2swy19rk/3ekJ3ZkwmXLmlVCRjEyt/bR
6uROHIX4HzK0La8JlU7gTgc77tZpC7uovbRQiMZOX8Waw0eIb9lqSMtKWJI8XgLG
v255LLb8qyaAbXBlq+D/ettUauAcJkEAWPSMuJ+WPkKuYotbyIXYBpELOa1f0EkF
/khUdCYob2Jak81cRURC7cY4JDWVa0qlLCWGYaKpTW4ACAajBrq1BSfAyrjFFuGS
XfBDj+0CSqtWo1ZR4Krpgg23xPFPWo07+TGhSAyqsbhmWfsHLqB9+kF930yZ/76+
cXI/zgFZ0pAXRzBIVxPCB7qN9AH+Zr8et4U2mn2Rc3PbpmZZflOw/spqOsXJe1XR
8i7+K3AkPtfeaGXqaDQI4y+uTi7Vq8tWwBwqDavThQtZH1kSfUfx5AiqNuvCnyUb
yLd/pDqgRr69GEo2YuS3T2HvK55hFtiDGZWjiSF1ddybcOtaT5s=
=tOrz
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: flycheck
Source-Version: 33~git20230824.e56e30d-1
Done: Sean Whitton 

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated flycheck 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, 31 Aug 2023 15:21:58 +0100
Source: flycheck
Architecture: source
Version: 33~git20230824.e56e30d-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen Team 
Changed-By: Sean Whitton 
Closes: 1013298 1050350 1050404
Changes:
 flycheck (33~git20230824.e56e30d-1) unstable; urgency=medium
 .
   [ Xiyue Deng ]
   * Sync to latest upstream HEAD.
   * Refresh patches.
 - Drop d/p/python3-in-test.patch.  Applied upstream.
   * Update d/watch to version 4 and track master branch.
   * Build-Depends on emacs-buttercup >=1.31~ to fix compatibility with
 Emacs 29+.  Closes: #1050350, #1050404.
   * Manually clean up instead of using "$(MAKE) clean" which depends on
 Eask.
   * Adopt package and add myself to uploaders.  Closes: 1013298.
 .
   [ Denis Danilov ]
   * Update copyright years.
 .
   [ Denis Danilov & Xiyue Deng ]
   * Update Standards-Version to 4.6.2.
 - Drop Built-Using field.
 .
   [ Sean Whitton ]
   * Drop test suite changes from previous two uploads.
Checksums-Sha1:
 ff394d9313dcb75d75a3bf166d97c57b7ecfec0d 2473 
flycheck_33~git20230824.e56e30d-1.dsc
 89ab1d71a80f5920bcb9c087074f749792a439ec 959060 
flycheck_33~git20230824.e56e30d.orig.tar.xz
 437165aecf95b41eb4e287e1967acda875ca10aa 22020 
flycheck_33~git20230824.e56e30d-1.debian.tar.xz
Checksums-Sha256:
 f4a0cd8483c415d48788dfa909927c70d5f70fd025d5490ea69692b2ef7b3e80 2473 
flycheck_33~git20230824.e56e30d-1.dsc
 8ccbe52abcd7320cae1a7dbe9293099aa10a0e57bd3f187ba04756edb9e6272a 959060 
flycheck_33~git20230824.e56e30d.orig.tar.xz
 844679530f59930195755dd9703b2ed6b9295d6aecd7495b0d8059bf4d6e2cab 22020 
flycheck_33~git20230824.e56e30d-1.debian.tar.xz
Files:
 b5ec970011f7907730c7d52d391ccdfa 2473 lisp optional 

Bug#1050404: marked as done (flycheck: keep flycheck out of testing)

[Debian Bug Tracking System]

Your message dated Thu, 31 Aug 2023 14:34:30 +
with message-id 
and subject line Bug#1050404: fixed in flycheck 33~git20230824.e56e30d-1
has caused the Debian Bug report #1050404,
regarding flycheck: keep flycheck out of testing
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.)


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

flycheck is unmaintained and its fragile autopkgtest keeps stopping more
important things from migrating to testing.  Let's keep it out of testing for 
now.

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: flycheck
Source-Version: 33~git20230824.e56e30d-1
Done: Sean Whitton 

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated flycheck 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, 31 Aug 2023 15:21:58 +0100
Source: flycheck
Architecture: source
Version: 33~git20230824.e56e30d-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen Team 
Changed-By: Sean Whitton 
Closes: 1013298 1050350 1050404
Changes:
 flycheck (33~git20230824.e56e30d-1) unstable; urgency=medium
 .
   [ Xiyue Deng ]
   * Sync to latest upstream HEAD.
   * Refresh patches.
 - Drop d/p/python3-in-test.patch.  Applied upstream.
   * Update d/watch to version 4 and track master branch.
   * Build-Depends on emacs-buttercup >=1.31~ to fix compatibility with
 Emacs 29+.  Closes: #1050350, #1050404.
   * Manually clean up instead of using "$(MAKE) clean" which depends on
 Eask.
   * Adopt package and add myself to uploaders.  Closes: 1013298.
 .
   [ Denis Danilov ]
   * Update copyright years.
 .
   [ Denis Danilov & Xiyue Deng ]
   * Update Standards-Version to 4.6.2.
 - Drop Built-Using field.
 .
   [ Sean Whitton ]
   * Drop test suite changes from previous two uploads.
Checksums-Sha1:
 ff394d9313dcb75d75a3bf166d97c57b7ecfec0d 2473 
flycheck_33~git20230824.e56e30d-1.dsc
 89ab1d71a80f5920bcb9c087074f749792a439ec 959060 
flycheck_33~git20230824.e56e30d.orig.tar.xz
 437165aecf95b41eb4e287e1967acda875ca10aa 22020 
flycheck_33~git20230824.e56e30d-1.debian.tar.xz
Checksums-Sha256:
 f4a0cd8483c415d48788dfa909927c70d5f70fd025d5490ea69692b2ef7b3e80 2473 
flycheck_33~git20230824.e56e30d-1.dsc
 8ccbe52abcd7320cae1a7dbe9293099aa10a0e57bd3f187ba04756edb9e6272a 959060 
flycheck_33~git20230824.e56e30d.orig.tar.xz
 844679530f59930195755dd9703b2ed6b9295d6aecd7495b0d8059bf4d6e2cab 22020 
flycheck_33~git20230824.e56e30d-1.debian.tar.xz
Files:
 b5ec970011f7907730c7d52d391ccdfa 2473 lisp optional 
flycheck_33~git20230824.e56e30d-1.dsc
 51853b968d0befdcf78ee402481489fc 959060 lisp optional 
flycheck_33~git20230824.e56e30d.orig.tar.xz
 3138c84e52701d77ebff8c392d5819f1 22020 lisp optional 
flycheck_33~git20230824.e56e30d-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmTwoiwACgkQaVt65L8G
YkCdnQ//T84TakAVuWvNAsEycSz28Z6l1D1fupSpLCIumAd0LslFBXDQGi4Ub+VP
grndtmuWoWXF2TTgK2y+5b8zGZ1x8mc3peOx36C60C2frseU+n1to4HO0xOSetTh
OZuCgvdWfkUYa34XJBGRiXAYbKLCbGUFYIseezK4+K6GXr7xGtm3E2s7nNp70tkh
c1OUG4PzrdInWMPdL8Uyuo5YNDMxFPfHvZqdnRKu6q2Na+E8W7eVcHUuv/54zjK2
53fPCfjaOLZXWY1+2d9/k3g1stULL5wQHLS3LH9JCx/kYu9BALRrQYUZfg785z83
CPqn3X9CLaOfdwmzUOpjYlIrIjSwTDfikFxrI4f8SzMWPahCFKTxdsdBPRYwkHB+
eaevlVAr3RkYh/agsV9Mw6Xew5xB3IgLVRRAEY2nFknXDeH6ysLsxZOAJkAZh9mU
fY6q06HaNsa9AdC9p1LToVHiqh2GZAoMIBgzgiXZ0mHPuzSWUVwjy0/KEnte7npm
hQm4vDOCPbg/QmGEsKvFEx/bQT6PZlFSDublhwIja+lzQtGsBQUcGPTT5mF95Wf5
xMv5bv7+DKuAJSdVSIL3JoHiWt9KC3UxUHuaXZeJbBcbda43YuWqQfY0pbJ4dYvW
5cKmPBo7zxq0ftOnOojl3Cbg9XLgh2yWrZ/nwJxF3M9/5eZpouo=
=Ozl7
-END PGP SIGNATURE End Message ---

Bug#1050404: marked as done (flycheck: keep flycheck out of testing)

[Debian Bug Tracking System]

Your message dated Thu, 31 Aug 2023 14:34:30 +
with message-id 
and subject line Bug#1050350: fixed in flycheck 33~git20230824.e56e30d-1
has caused the Debian Bug report #1050350,
regarding flycheck: keep flycheck out of testing
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.)


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

flycheck is unmaintained and its fragile autopkgtest keeps stopping more
important things from migrating to testing.  Let's keep it out of testing for 
now.

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: flycheck
Source-Version: 33~git20230824.e56e30d-1
Done: Sean Whitton 

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated flycheck 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, 31 Aug 2023 15:21:58 +0100
Source: flycheck
Architecture: source
Version: 33~git20230824.e56e30d-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen Team 
Changed-By: Sean Whitton 
Closes: 1013298 1050350 1050404
Changes:
 flycheck (33~git20230824.e56e30d-1) unstable; urgency=medium
 .
   [ Xiyue Deng ]
   * Sync to latest upstream HEAD.
   * Refresh patches.
 - Drop d/p/python3-in-test.patch.  Applied upstream.
   * Update d/watch to version 4 and track master branch.
   * Build-Depends on emacs-buttercup >=1.31~ to fix compatibility with
 Emacs 29+.  Closes: #1050350, #1050404.
   * Manually clean up instead of using "$(MAKE) clean" which depends on
 Eask.
   * Adopt package and add myself to uploaders.  Closes: 1013298.
 .
   [ Denis Danilov ]
   * Update copyright years.
 .
   [ Denis Danilov & Xiyue Deng ]
   * Update Standards-Version to 4.6.2.
 - Drop Built-Using field.
 .
   [ Sean Whitton ]
   * Drop test suite changes from previous two uploads.
Checksums-Sha1:
 ff394d9313dcb75d75a3bf166d97c57b7ecfec0d 2473 
flycheck_33~git20230824.e56e30d-1.dsc
 89ab1d71a80f5920bcb9c087074f749792a439ec 959060 
flycheck_33~git20230824.e56e30d.orig.tar.xz
 437165aecf95b41eb4e287e1967acda875ca10aa 22020 
flycheck_33~git20230824.e56e30d-1.debian.tar.xz
Checksums-Sha256:
 f4a0cd8483c415d48788dfa909927c70d5f70fd025d5490ea69692b2ef7b3e80 2473 
flycheck_33~git20230824.e56e30d-1.dsc
 8ccbe52abcd7320cae1a7dbe9293099aa10a0e57bd3f187ba04756edb9e6272a 959060 
flycheck_33~git20230824.e56e30d.orig.tar.xz
 844679530f59930195755dd9703b2ed6b9295d6aecd7495b0d8059bf4d6e2cab 22020 
flycheck_33~git20230824.e56e30d-1.debian.tar.xz
Files:
 b5ec970011f7907730c7d52d391ccdfa 2473 lisp optional 
flycheck_33~git20230824.e56e30d-1.dsc
 51853b968d0befdcf78ee402481489fc 959060 lisp optional 
flycheck_33~git20230824.e56e30d.orig.tar.xz
 3138c84e52701d77ebff8c392d5819f1 22020 lisp optional 
flycheck_33~git20230824.e56e30d-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmTwoiwACgkQaVt65L8G
YkCdnQ//T84TakAVuWvNAsEycSz28Z6l1D1fupSpLCIumAd0LslFBXDQGi4Ub+VP
grndtmuWoWXF2TTgK2y+5b8zGZ1x8mc3peOx36C60C2frseU+n1to4HO0xOSetTh
OZuCgvdWfkUYa34XJBGRiXAYbKLCbGUFYIseezK4+K6GXr7xGtm3E2s7nNp70tkh
c1OUG4PzrdInWMPdL8Uyuo5YNDMxFPfHvZqdnRKu6q2Na+E8W7eVcHUuv/54zjK2
53fPCfjaOLZXWY1+2d9/k3g1stULL5wQHLS3LH9JCx/kYu9BALRrQYUZfg785z83
CPqn3X9CLaOfdwmzUOpjYlIrIjSwTDfikFxrI4f8SzMWPahCFKTxdsdBPRYwkHB+
eaevlVAr3RkYh/agsV9Mw6Xew5xB3IgLVRRAEY2nFknXDeH6ysLsxZOAJkAZh9mU
fY6q06HaNsa9AdC9p1LToVHiqh2GZAoMIBgzgiXZ0mHPuzSWUVwjy0/KEnte7npm
hQm4vDOCPbg/QmGEsKvFEx/bQT6PZlFSDublhwIja+lzQtGsBQUcGPTT5mF95Wf5
xMv5bv7+DKuAJSdVSIL3JoHiWt9KC3UxUHuaXZeJbBcbda43YuWqQfY0pbJ4dYvW
5cKmPBo7zxq0ftOnOojl3Cbg9XLgh2yWrZ/nwJxF3M9/5eZpouo=
=Ozl7
-END PGP SIGNATURE End Message ---

Bug#1050350: marked as done (flycheck: keep flycheck out of testing until it finds an uploader)

[Debian Bug Tracking System]

Your message dated Thu, 31 Aug 2023 14:34:30 +
with message-id 
and subject line Bug#1050350: fixed in flycheck 33~git20230824.e56e30d-1
has caused the Debian Bug report #1050350,
regarding flycheck: keep flycheck out of testing until it finds an uploader
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.)


-- 
1050350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flycheck
Severity: serious
Justification: Team decision
X-Debbugs-Cc: debian-emac...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Nobody has stepped up to take care of flycheck, and it currently
blocks the transition of emacs 29 to testing. 

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

Kernel: Linux 6.3.0-1-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmTmA08ACgkQA0U5G1Wq
FSFx4RAAug0/SVS+L2nFAKwRHgsqypfuSZ46JP+ayMV+O3yLc2vyZy6HOgt1Ew7c
Psfjt3s3ba2adbOZraPT0CAx2Dgz/0cKg2Rm4M6fMOCwYsqjwNSlPpE8rw0o0k5i
xPV5x+WKpoGWQB4sWW3QqDmZEdU3OY3szkpCKxDnR2Dk4rGRXBbI1utH4DOpdT8R
fCN6Qg+MWtimK+M33n/nklxvK8Ze7RLo2swy19rk/3ekJ3ZkwmXLmlVCRjEyt/bR
6uROHIX4HzK0La8JlU7gTgc77tZpC7uovbRQiMZOX8Waw0eIb9lqSMtKWJI8XgLG
v255LLb8qyaAbXBlq+D/ettUauAcJkEAWPSMuJ+WPkKuYotbyIXYBpELOa1f0EkF
/khUdCYob2Jak81cRURC7cY4JDWVa0qlLCWGYaKpTW4ACAajBrq1BSfAyrjFFuGS
XfBDj+0CSqtWo1ZR4Krpgg23xPFPWo07+TGhSAyqsbhmWfsHLqB9+kF930yZ/76+
cXI/zgFZ0pAXRzBIVxPCB7qN9AH+Zr8et4U2mn2Rc3PbpmZZflOw/spqOsXJe1XR
8i7+K3AkPtfeaGXqaDQI4y+uTi7Vq8tWwBwqDavThQtZH1kSfUfx5AiqNuvCnyUb
yLd/pDqgRr69GEo2YuS3T2HvK55hFtiDGZWjiSF1ddybcOtaT5s=
=tOrz
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: flycheck
Source-Version: 33~git20230824.e56e30d-1
Done: Sean Whitton 

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated flycheck 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, 31 Aug 2023 15:21:58 +0100
Source: flycheck
Architecture: source
Version: 33~git20230824.e56e30d-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen Team 
Changed-By: Sean Whitton 
Closes: 1013298 1050350 1050404
Changes:
 flycheck (33~git20230824.e56e30d-1) unstable; urgency=medium
 .
   [ Xiyue Deng ]
   * Sync to latest upstream HEAD.
   * Refresh patches.
 - Drop d/p/python3-in-test.patch.  Applied upstream.
   * Update d/watch to version 4 and track master branch.
   * Build-Depends on emacs-buttercup >=1.31~ to fix compatibility with
 Emacs 29+.  Closes: #1050350, #1050404.
   * Manually clean up instead of using "$(MAKE) clean" which depends on
 Eask.
   * Adopt package and add myself to uploaders.  Closes: 1013298.
 .
   [ Denis Danilov ]
   * Update copyright years.
 .
   [ Denis Danilov & Xiyue Deng ]
   * Update Standards-Version to 4.6.2.
 - Drop Built-Using field.
 .
   [ Sean Whitton ]
   * Drop test suite changes from previous two uploads.
Checksums-Sha1:
 ff394d9313dcb75d75a3bf166d97c57b7ecfec0d 2473 
flycheck_33~git20230824.e56e30d-1.dsc
 89ab1d71a80f5920bcb9c087074f749792a439ec 959060 
flycheck_33~git20230824.e56e30d.orig.tar.xz
 437165aecf95b41eb4e287e1967acda875ca10aa 22020 
flycheck_33~git20230824.e56e30d-1.debian.tar.xz
Checksums-Sha256:
 f4a0cd8483c415d48788dfa909927c70d5f70fd025d5490ea69692b2ef7b3e80 2473 
flycheck_33~git20230824.e56e30d-1.dsc
 8ccbe52abcd7320cae1a7dbe9293099aa10a0e57bd3f187ba04756edb9e6272a 959060 
flycheck_33~git20230824.e56e30d.orig.tar.xz
 844679530f59930195755dd9703b2ed6b9295d6aecd7495b0d8059bf4d6e2cab 22020 
flycheck_33~git20230824.e56e30d-1.debian.tar.xz
Files:
 b5ec970011f7907730c7d52d391ccdfa 2473 lisp optional 

Bug#1042933: octave-statistics autopkg tests fail in unstable on amd64

[Rafael Laboissière]

* Rafael Laboissière  [2023-08-31 15:01]:


* Sébastien Villemot  [2023-08-31 12:05]:


Le jeudi 03 août 2023 à 08:33 +0200, Rafael Laboissière a écrit :


Just for the record, this is the offending unit test:

308s [inst/ConfusionMatrixChart.m]
308s >

/tmp/autopkgtest-lxc.9x_h6bvs/downtmp/build.BGX/src/inst/ConfusionMatrixChart.m
308s * demo
308s  ## Create a simple ConfusionMatrixChart Object
308s
308s  cm = ConfusionMatrixChart (gca, [1 2; 1 2], {"A","B"},{"XLabel","LABEL 
A"})
308s  NormalizedValues = cm.NormalizedValues
308s  ClassLabels = cm.ClassLabels
308s * shared visibility_setting
308s  visibility_setting = get (0, "DefaultFigureVisible");
308s * test
308s  set (0, "DefaultFigureVisible", "off");
308s  cm = ConfusionMatrixChart (gca, [1 2; 1 2], {"A","B"},{"XLabel","LABEL 
A"});
308s  assert (isa (cm, "ConfusionMatrixChart"), true);
308s  set (0, "DefaultFigureVisible", visibility_setting);
308s warning: Non-positive limit for logarithmic axis ignored
308s ! test failed
308s set: "cameratarget" must be finite
308s shared variables visibility_setting = on
308s 1 test, 0 passed, 0 known failure, 0 skipped

We have seen this problem already elsewhere. I will try to 
investigate it.


Did you get to a conclusion?


No progress on my side, sorry.


At any rate, the last autopkgtest run (on 2023-08-26) succeded: 
https://ci.debian.net/data/autopkgtest/unstable/amd64/o/octave-statistics/37186503/log.gz


Should we close this bug report?

Rafael Laboissière

Bug#1042933: octave-statistics autopkg tests fail in unstable on amd64

[Rafael Laboissière]

* Sébastien Villemot  [2023-08-31 12:05]:


Le jeudi 03 août 2023 à 08:33 +0200, Rafael Laboissière a écrit :


Just for the record, this is the offending unit test:

 308s [inst/ConfusionMatrixChart.m]
 308s >
 
/tmp/autopkgtest-lxc.9x_h6bvs/downtmp/build.BGX/src/inst/ConfusionMatrixChart.m
 308s * demo
 308s  ## Create a simple ConfusionMatrixChart Object
 308s
 308s  cm = ConfusionMatrixChart (gca, [1 2; 1 2], {"A","B"},{"XLabel","LABEL 
A"})
 308s  NormalizedValues = cm.NormalizedValues
 308s  ClassLabels = cm.ClassLabels
 308s * shared visibility_setting
 308s  visibility_setting = get (0, "DefaultFigureVisible");
 308s * test
 308s  set (0, "DefaultFigureVisible", "off");
 308s  cm = ConfusionMatrixChart (gca, [1 2; 1 2], {"A","B"},{"XLabel","LABEL 
A"});
 308s  assert (isa (cm, "ConfusionMatrixChart"), true);
 308s  set (0, "DefaultFigureVisible", visibility_setting);
 308s warning: Non-positive limit for logarithmic axis ignored
 308s ! test failed
 308s set: "cameratarget" must be finite
 308s shared variables visibility_setting = on
 308s 1 test, 0 passed, 0 known failure, 0 skipped

We have seen this problem already elsewhere. I will try to investigate 
it.


Did you get to a conclusion?


No progress on my side, sorry.

Rafael Laboissière

Bug#1050922: mir: autopkgtest regression

[Sebastian Ramacher]

Source: mir
Version: 2.14.1-4
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mir/37255901/log.gz

 53s [--] Global test environment tear-down
 53s [==] 1018 tests from 52 test cases run. (25858ms total elapsed)
 53s [  PASSED  ] 998 tests
 53s [  SKIPPED ] 9 tests skipped:
 53s [  SKIPPED ] SelfTest.acquiring_unsupported_extension_is_xfail
 53s [  SKIPPED ] SelfTest.acquiring_unsupported_extension_version_is_xfail
 53s [  SKIPPED ] SelfTest.expected_missing_extension_is_xfail
 53s [  SKIPPED ] GtkPrimarySelection.source_can_supply_request
 53s [  SKIPPED ] GtkPrimarySelection.source_sees_request
 53s [  SKIPPED ] SelfTest.xfail_failure_is_noted
 53s [  SKIPPED ] GtkPrimarySelection.sink_can_listen
 53s [  SKIPPED ] GtkPrimarySelection.sink_can_request
 53s [  SKIPPED ] GtkPrimarySelection.source_can_offer
 53s [  FAILED  ] 11 tests failed:
 53s [  FAILED  ] 
VirtualPointerV1Test.when_virutal_pointer_is_moved_with_absolute_coordinates_with_the_extent_twice_of_the_output_client_sees_motion
 53s [  FAILED  ] 
VirtualPointerV1Test.when_virutal_pointer_scrolls_with_steps_client_sees_axis_descrete
 53s [  FAILED  ] 
VirtualPointerV1Test.when_virutal_pointer_scrolls_client_sees_axis
 53s [  FAILED  ] 
VirtualPointerV1Test.when_virutal_pointer_given_multiple_button_presses_at_once_client_sees_all
 53s [  FAILED  ] 
VirtualPointerV1Test.when_virutal_pointer_left_releases_client_sees_button_up
 53s [  FAILED  ] 
VirtualPointerV1Test.when_virutal_pointer_left_clicks_client_sees_button_down
 53s [  FAILED  ] 
VirtualPointerV1Test.when_virutal_pointer_is_moved_multiple_times_client_sees_motion
 53s [  FAILED  ] 
VirtualPointerV1Test.when_virutal_pointer_is_moved_client_sees_motion
 53s [  FAILED  ] 
VirtualPointerV1Test.when_virutal_pointer_is_moved_with_absolute_coordinates_with_the_extent_of_the_output_client_sees_motion
 53s [  FAILED  ] 
VirtualPointerV1Test.when_virutal_pointer_presses_and_releases_different_buttons_on_same_frame_client_sees_correct_events
 53s [  FAILED  ] ClientSurfaceEventsTest.frame_timestamp_increases
 54s autopkgtest [12:09:41]: test wlcs: ---]
 54s autopkgtest [12:09:41]: test wlcs:  - - - - - - - - - - results - - - - - 
- - - - -
 54s wlcs FAIL non-zero exit status 1
 54s autopkgtest [12:09:41]:  summary
 54s wlcs FAIL non-zero exit status 1

Cheers
-- 
Sebastian Ramacher

Bug#1050921: ignition-common: FTBFS on !amd64, !i386

[Sebastian Ramacher]

Source: ignition-common
Version: 4.7.0+ds2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=ignition-common=arm64=4.7.0%2Bds2-1=1691771151=0

[ 17%] Building CXX object src/CMakeFiles/ignition-common4.dir/WorkerPool.cc.o
cd /<>/obj-aarch64-linux-gnu/src && /usr/bin/c++ 
-Dignition_common4_EXPORTS -I/<>/include 
-I/<>/obj-aarch64-linux-gnu/include 
-I/<>/obj-aarch64-linux-gnu/core/include 
-I/usr/include/ignition/math6 -isystem /usr/include/uuid -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -fPIC 
-I/usr/include/uuid -MD -MT src/CMakeFiles/ignition-common4.dir/WorkerPool.cc.o 
-MF CMakeFiles/ignition-common4.dir/WorkerPool.cc.o.d -o 
CMakeFiles/ignition-common4.dir/WorkerPool.cc.o -c 
/<>/src/WorkerPool.cc
/<>/src/WorkerPool.cc:24:10: fatal error: gz/math/Helpers.hh: No 
such file or directory
   24 | #include "gz/math/Helpers.hh"
  |  ^~~~
compilation terminated.
make[3]: *** [src/CMakeFiles/ignition-common4.dir/build.make:317: 
src/CMakeFiles/ignition-common4.dir/WorkerPool.cc.o] Error 1
make[3]: *** Waiting for unfinished jobs

Cheers
-- 
Sebastian Ramacher

Bug#1050903: telegram-desktop: segmentation fault

[Leandro Cunha]

Hi,

On Thu, Aug 31, 2023 at 7:42 AM Leandro Cunha  wrote:
>
> Hi,
>
> With:
>
> env QT_QPA_PLATFORMTHEME=xcb telegram-desktop -- %u
>
> Application works normally.
>
> --
> Cheers,
> Leandro Cunha

Still experiencing segmentation faults for users with stories.

-- 
Cheers,
Leandro Cunha

Bug#1050903: telegram-desktop: segmentation fault

[Leandro Cunha]

Hi,

With:

env QT_QPA_PLATFORMTHEME=xcb telegram-desktop -- %u

Application works normally.

-- 
Cheers,
Leandro Cunha

Bug#1050903: telegram-desktop: segmentation fault

[Leandro Cunha]

Package: telegram-desktop
Version:  4.9.3+ds-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Package again presents segmentation fault in some features like
viewing the user profile.

The same user has views of stories that do not get to be listed with
the application presenting a segmentation fault afterwards.

telegram-desktop -debug

(telegram-desktop:8895): Telegram-WARNING **: 07:23:35.375:
Application has been built with foreign rlottie, animated emojis won't
be colored t
o the selected pack.

(telegram-desktop:8895): Telegram-WARNING **: 07:23:35.375:
Application was built without embedded fonts, this may lead to font
issues. On Debi
an-based systems, make sure you have the fonts-open-sans package installed
QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter
qt.svg: Error while inflating gzip file: SVG format check failed
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Falha de segmentação (imagem do núcleo gravada)

-- Package-specific info:

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

Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages telegram-desktop depends on:
ii  libabsl2022062320220623.1-3
ii  libavcodec60   7:6.0-6
ii  libavfilter9   7:6.0-6
ii  libavformat60  7:6.0-6
ii  libavutil587:6.0-6
ii  libc6  2.37-7
ii  libgcc-s1  13.2.0-2
ii  libglib2.0-0   2.77.2-1
ii  libglibmm-2.68-1   2.77.0-1
ii  libhunspell-1.7-0  1.7.2+really1.7.2-10
ii  libjpeg62-turbo1:2.1.5-2
ii  libkf5coreaddons5  5.107.0-1
ii  liblz4-1   1.9.4-1
ii  libminizip11:1.2.13.dfsg-3
ii  libopenal1 1:1.23.1-3
ii  libopus0   1.4-1
ii  libqrcodegencpp1   1.8.0-1.1
ii  libqt5core5a [qtbase-abi-5-15-10]  5.15.10+dfsg-3
ii  libqt5gui5 5.15.10+dfsg-3
ii  libqt5network5 5.15.10+dfsg-3
ii  libqt5svg5 5.15.10-2
ii  libqt5widgets5 5.15.10+dfsg-3
ii  librlottie0-1  0.1+dfsg-4
ii  libsigc++-3.0-03.4.0-7
ii  libsrtp2-1 2.5.0-3
ii  libssl33.0.10-1
ii  libstdc++6 13.2.0-2
ii  libswresample4 7:6.0-6
ii  libswscale77:6.0-6
ii  libvpx71.12.0-1
ii  libx11-6   2:1.8.6-1
ii  libxcb-keysyms10.4.0-1+b2
ii  libxcb-record0 1.15-1
ii  libxcb-screensaver01.15-1
ii  libxcb11.15-1
ii  libxcomposite1 1:0.4.5-1
ii  libxdamage11:1.1.6-1
ii  libxext6   2:1.3.4-1+b1
ii  libxfixes3 1:6.0.0-2
ii  libxrandr2 2:1.5.2-2+b1
ii  libxtst6   2:1.2.3-1.1
ii  libxxhash0 0.8.1-1
ii  libyuv00.0~git20230616.a366ad7-1
ii  qt5-image-formats-plugins  5.15.10-2
ii  zlib1g 1:1.2.13.dfsg-3

Versions of packages telegram-desktop recommends:
ii  fonts-open-sans   1.11-2
ii  libwebkit2gtk-4.0-37  2.40.5-1

telegram-desktop suggests no packages.

Versions of packages telegram-desktop is related to:
ii  xdg-desktop-portal   1.16.0-3
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend]  1.14.1-1
ii  xdg-desktop-portal-kde [xdg-desktop-portal-backend]  5.27.7-1

-- no debconf information
-BEGIN PGP PUBLIC KEY BLOCK-

mQINBF/gQ8gBEADHVKgoWsUWNGVvR6sMhBPUdBUEH+QALpr1QYXhetBfRwaY0HWN
pKgejHdxKO8H+kIhRMoh89CCKg3hAJ9LmOOTXkX7U5/Cya/zRMKk5zBD3rKIaugh
0XYT15Nz1jwL7TIDG25yPSloDtVgVXTep0ZzKsNYJjb4OAqa88cvUEJEhhqrldlR
gpNbkixEh5ituO8pMShEBWqLs3yt4Hr1VFWnTIm4dl/JLBHpexzubDOw/mKCTpNd
A1JGHTvce1wtJ2fMzCVzhEjd5pyjLZV/o8hVw2/ON/yXvpJuz0lV/hiW0M+cDcas
sKftErtsZpRy3wwXdkBcJt6soYuqfCHwgMfL2iC6mPviE8xWAHMOmhdC3wDskZpb
RcLfH5IMYajJAGRO/GCMcKKbq7WkEOeloivtg64xBlYuJf9aOcHKP/8R3EObiNp7
ubQAJtV3pEGD4mx1mhutFxDHB+CfnxE3dWvxZSV9y1n4UOzkDJ3kDx5Ee0MbRvJD
w6aXKc6dhYREgh7hLDcMFz+3LcBiZDLxI3g+SHe3Bl61vdsnPno+0HhCzvB+fL4S
eoy7Myfiunz9BrB2HPN+wNCT0YgV+Kv8QoDGzBwos5H1vUJSY4t59w6xoXAYUsAm

Bug#1050902: librust-multihash-dev: impossible to install: depends on missing package librust-unsigned-varint-0.5+default-dev

[Jonas Smedegaard]

Package: librust-multihash-dev
Version: 0.11.4-2
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As subject says: package is impossible to install as it depends on
unavailable package librust-unsigned-varint-0.5+default-dev.

- -  Jonas
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTwaVwACgkQLHwxRsGg
ASG1PA//SkSyoQA7WZn6HBP24mmHEUEEvrcNQmiohbWEGqcG6PSlKOGIgnpQkaQT
t/MDbpHPsDuI9gU7zTsHxN5wtMre1q1XqHFrtSTElVdFsILtsdo+kOnKTRySWBWe
RqjwLi7+dgiDOApaoZyV+KLPDCAbrnwuyCFQPpcz/AlWqOqwhZEyLCqZM3AFSDFM
B0+7UejI4/PqXyFstqGZTxEjeDjlBCAyNhvGggLFjkNE9w1DBIMILFleLJYCtKZu
vcD5g3fXpjNRHqoCRW013r1wr9017NyPBUL+y+ZpEbhTBGI7XWlGG3/5cbhgakkJ
eDnjRml+tu+CUpHAjNOPtl/zLg+j4bKll3TDEzmItFThNEXLfiGA5Gl68oydOPZF
0a2VPtZ32XftrRyQHOuxuDfMf04qeshkJZSDT8+gGBG+hQLJTZ8RH97W2kfdOcq0
A3Fnzw+iq7kFAP1AsYpbBIw3p1dI27hpBlnT9aVrAQD9/P6OMyRuoXZxngDH6LB+
HqQK7r/mdOvNQkCbkBZZpWv0ckJtGMYTDDOfd+7Q/sX4LZpgpDm8oHTLGOrdwX/1
LiindD4EfHYThYe7otkdN9FJL403GuV67fuw8Pa7TPZnqA9dfFw+JKg4oTEVN757
cLMXtrhvJuaVbysvPS5fN0YUJVTdleL7ss/dZRlZF6CpSkmCKNo=
=C/HN
-END PGP SIGNATURE-

Bug#1042933: octave-statistics autopkg tests fail in unstable on amd64

[Sébastien Villemot]

Le jeudi 03 août 2023 à 08:33 +0200, Rafael Laboissière a écrit :
> * Matthias Klose  [2023-08-03 04:23]:
> 
> > Package: src:octave-statistics
> > Version: 1.6.0-1
> > Severity: serious
> > Tags: sid trixie
> > 
> > octave autopkg tests fail in unstable on amd64 (triggered by gcc-13).
> > 
> > https://ci.debian.net/data/autopkgtest/testing/amd64/o/octave-statistics/36329437/log.gz
> > 
> > Not sure which ones are the regressions, because all failures seem to 
> > be marked as "known failure".
> 
> Thanks for the bug report, Matthias.
> 
> Just for the record, this is the offending unit test:
> 
>  308s [inst/ConfusionMatrixChart.m]
>  308s >
>  
> /tmp/autopkgtest-lxc.9x_h6bvs/downtmp/build.BGX/src/inst/ConfusionMatrixChart.m
>  308s * demo
>  308s  ## Create a simple ConfusionMatrixChart Object
>  308s
>  308s  cm = ConfusionMatrixChart (gca, [1 2; 1 2], 
> {"A","B"},{"XLabel","LABEL A"})
>  308s  NormalizedValues = cm.NormalizedValues
>  308s  ClassLabels = cm.ClassLabels
>  308s * shared visibility_setting
>  308s  visibility_setting = get (0, "DefaultFigureVisible");
>  308s * test
>  308s  set (0, "DefaultFigureVisible", "off");
>  308s  cm = ConfusionMatrixChart (gca, [1 2; 1 2], 
> {"A","B"},{"XLabel","LABEL A"});
>  308s  assert (isa (cm, "ConfusionMatrixChart"), true);
>  308s  set (0, "DefaultFigureVisible", visibility_setting);
>  308s warning: Non-positive limit for logarithmic axis ignored
>  308s ! test failed
>  308s set: "cameratarget" must be finite
>  308s shared variables visibility_setting = on
>  308s 1 test, 0 passed, 0 known failure, 0 skipped
> 
> We have seen this problem already elsewhere. I will try to investigate 
> it.

Did you get to a conclusion?

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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

Bug#1050900: FTBFS: cannot find package "github.com/cheggaaa/pb"

[Shengjing Zhu]

Source: aptly
Version: 1.5.0+ds1-1
Severity: serious
Tags: ftbfs trixie sid patch
X-Debbugs-Cc: z...@debian.org

src/github.com/aptly-dev/aptly/console/progress.go:9:2: cannot find package 
"github.com/cheggaaa/pb" in any of:
/usr/lib/go-1.21/src/github.com/cheggaaa/pb (from $GOROOT)
/<>/obj-x86_64-linux-gnu/src/github.com/cheggaaa/pb (from 
$GOPATH)

It's because golang-gopkg-cheggaaa-pb.v1-dev remove this compatible symlink
which is conflict with golang-github-cheggaaa-pb-dev package.

Please see the patch
https://salsa.debian.org/debian/aptly/-/merge_requests/11


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

Kernel: Linux 6.4.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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#1050898: src:tpm2-pytss: fails to migrate to testing for too long: FTBFS on s390x

[Paul Gevers]

Source: tpm2-pytss
Version: 1.2.0-3
Severity: serious
Control: close -1 2.1.0-1
Tags: sid trixie ftbfs
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 30 days as having a Release Critical bug in 
testing [1]. Your package src:tpm2-pytss has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable failed 
to build on s390x (test failure).


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 immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, 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/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=tpm2-pytss



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:tpm2-pytss: fails to migrate to testing for too long: FTBFS on s390x

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.1.0-1
Bug #1050898 [src:tpm2-pytss] src:tpm2-pytss: fails to migrate to testing for 
too long: FTBFS on s390x
Marked as fixed in versions tpm2-pytss/2.1.0-1.
Bug #1050898 [src:tpm2-pytss] src:tpm2-pytss: fails to migrate to testing for 
too long: FTBFS on s390x
Marked Bug as done

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

Bug#1050891: marked as done (sccache - update for new addr2line.)

[Debian Bug Tracking System]

Your message dated Thu, 31 Aug 2023 09:06:54 +
with message-id 
and subject line Bug#1050891: fixed in sccache 0.5.4-12
has caused the Debian Bug report #1050891,
regarding sccache - update for new addr2line.
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.)


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

Package: sccache
Version: 0.5.4-11
Severity: serious
Tags: patch

I just updated addr2line to version 0.20.0, sccache builds succesfully
with the new version after bumping the dependency.

Debdiff attatched.
diff -Nru sccache-0.5.4/debian/changelog sccache-0.5.4/debian/changelog
--- sccache-0.5.4/debian/changelog  2023-08-24 08:23:51.0 +
+++ sccache-0.5.4/debian/changelog  2023-08-28 13:25:35.0 +
@@ -1,3 +1,10 @@
+sccache (0.5.4-11.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Bump dependency on object crate to 0.31.
+
+ -- nobody   Mon, 28 Aug 2023 13:25:35 +
+
 sccache (0.5.4-11) unstable; urgency=medium
 
   * drop patch 2018, obsoleted by Debian package changes
diff -Nru sccache-0.5.4/debian/control sccache-0.5.4/debian/control
--- sccache-0.5.4/debian/control2023-08-13 09:04:02.0 +
+++ sccache-0.5.4/debian/control2023-08-28 13:15:03.0 +
@@ -44,7 +44,7 @@
  librust-mime-0.3+default-dev,
  librust-num-cpus-1+default-dev,
  librust-number-prefix-0.4+default-dev,
- librust-object-0.30+default-dev,
+ librust-object-0.31+default-dev,
  librust-once-cell-1+default-dev (>= 1.17),
  librust-predicates-2+default-dev ,
  librust-rand-0.8+default-dev,
diff -Nru sccache-0.5.4/debian/patches/1007_update_object.patch 
sccache-0.5.4/debian/patches/1007_update_object.patch
--- sccache-0.5.4/debian/patches/1007_update_object.patch   1970-01-01 
00:00:00.0 +
+++ sccache-0.5.4/debian/patches/1007_update_object.patch   2023-08-28 
13:17:51.0 +
@@ -0,0 +1,7 @@
+Index: sccache-0.5.4/Cargo.toml
+===
+--- sccache-0.5.4.orig/Cargo.toml
 sccache-0.5.4/Cargo.toml
+@@ -92,1 +92,1 @@ zip = { version = "0.6", default-feature
+-object = "0.30"
++object = "0.31"
diff -Nru sccache-0.5.4/debian/patches/2001_no_dist-server.patch 
sccache-0.5.4/debian/patches/2001_no_dist-server.patch
--- sccache-0.5.4/debian/patches/2001_no_dist-server.patch  2023-08-24 
08:23:51.0 +
+++ sccache-0.5.4/debian/patches/2001_no_dist-server.patch  2023-08-28 
13:18:19.0 +
@@ -30,7 +30,7 @@
 -# dist-server only
  memmap2 = "0.6.2"
 -nix = { version = "0.26.2", optional = true }
- object = "0.30"
+ object = "0.31"
 -rouille = { version = "3.5", optional = true, default-features = false, 
features = [
 -  "ssl",
 -] }
diff -Nru sccache-0.5.4/debian/patches/2008_assert_cmd.patch 
sccache-0.5.4/debian/patches/2008_assert_cmd.patch
--- sccache-0.5.4/debian/patches/2008_assert_cmd.patch  2023-08-24 
08:23:51.0 +
+++ sccache-0.5.4/debian/patches/2008_assert_cmd.patch  2023-08-28 
13:18:39.0 +
@@ -8,7 +8,7 @@
 --- a/Cargo.toml
 +++ b/Cargo.toml
 @@ -100,7 +100,7 @@
- object = "0.30"
+ object = "0.31"
  
  [dev-dependencies]
 -assert_cmd = "2.0.10"
diff -Nru sccache-0.5.4/debian/patches/2017_memmap2.patch 
sccache-0.5.4/debian/patches/2017_memmap2.patch
--- sccache-0.5.4/debian/patches/2017_memmap2.patch 2023-08-24 
08:23:51.0 +
+++ sccache-0.5.4/debian/patches/2017_memmap2.patch 2023-08-28 
13:19:01.0 +
@@ -13,6 +13,6 @@
  
 -memmap2 = "0.6.2"
 +memmap2 = ">= 0.5.10, < 0.7"
- object = "0.30"
+ object = "0.31"
  
  [dev-dependencies]
diff -Nru sccache-0.5.4/debian/patches/series 
sccache-0.5.4/debian/patches/series
--- sccache-0.5.4/debian/patches/series 2023-08-18 15:13:19.0 +
+++ sccache-0.5.4/debian/patches/series 2023-08-28 13:16:36.0 +
@@ -1,5 +1,6 @@
 1001_optional_tests.patch
 1006_tests_network.patch
+1007_update_object.patch
 2001_no_dist-server.patch
 2002_no_opendal_backends.patch
 2003_no_windows.patch
--- End Message ---
--- Begin Message ---
Source: sccache
Source-Version: 0.5.4-12
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
sccache, 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 1050...@bugs.debian.org,
and the 

Bug#1050896: packagesearch: Incomplete/Misleading copyright file

[Julian Andres Klode]

Source: packagesearch
Version: 2.8.0
Severity: serious
X-Debbugs-Cc: j...@debian.org


The copyright file only states that it is licensed under the GPL,
but not which versions. This seems to imply it is licensed under
the GPL version 1.

The code meanwhile ships the GPL-2 in COPYING.

It's unclear whether the code is GPL-3 compatible. I'm not sure
this can be said, as there have been contributors aside from
the maintainer.

My advise would be to contact all the copyright holders, and
make sure that everyone is onboard with this actually being
GPL-2+ such that when dependencies update to GPL-3 or later
versions, you still remain compatible.

I am not sure if this bug can be reasonably solved right now,
maybe the copyright file can be changed to say GPL-2, I'd certainly
also advise using the machine-readable copyright format for it
to make everything clear rather than this half-assed free form.

The problem to consider with updating the copyright file to just
say GPL-2 is whether contributors knew they were contributing to
a GPL-2 codebase or whether they contributed thinking it was GPL-1.

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

Kernel: Linux 6.3.0-7-generic (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1050891: sccache - update for new addr2line.

[Jonas Smedegaard]

Quoting Peter Michael Green (2023-08-31 02:01:53)
> Package: sccache
> Version: 0.5.4-11
> Severity: serious
> Tags: patch
> 
> I just updated addr2line to version 0.20.0, sccache builds succesfully
> with the new version after bumping the dependency.
> 
> Debdiff attatched.

Please, pretty please, DO NOT BREAK REVERSE DEPENDENCIES uncoordinated.

Cc'ing debian-devel, to raise awareness of this ongoing pattern.

It is stressful.  You cannot expect to to always react quickly, and it
is not acceptable to use NMUs to paper over too sloppy coordination.

Possibly you did your homework and your assessment about the magnitude
of the damage is correct, but it is a risky game, and it is unfair:
Allow those responsible for maintaining packages to actually do that.

All that said, thanks for your bugreport, and for your tests.

Please in future coordinate *before* doing breaking changes (unless it
happens accidentally, of course).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Processed: reassign 1042141 to src:rust-log, forcibly merging 1040837 1042141

[Debian Bug Tracking System]

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

> reassign 1042141 src:rust-log
Bug #1042141 [src:rust-kv-log-macro] rust-kv-log-macro: FTBFS: unsatisfiable 
build-dependencies
Bug reassigned from package 'src:rust-kv-log-macro' to 'src:rust-log'.
No longer marked as found in versions rust-kv-log-macro/1.0.8-2.
Ignoring request to alter fixed versions of bug #1042141 to the same values 
previously set
> forcemerge 1040837 1042141
Bug #1040837 {Done: Peter Michael Green } [src:rust-log] 
rust-log: breaks API without coordination
Bug #1040837 {Done: Peter Michael Green } [src:rust-log] 
rust-log: breaks API without coordination
Added tag(s) ftbfs.
Bug #1042141 [src:rust-log] rust-kv-log-macro: FTBFS: unsatisfiable 
build-dependencies
1043386 was blocked by: 1040835 1040995 1040837
1043386 was not blocking any bugs.
Added blocking bug(s) of 1043386: 1042141
Marked Bug as done
Added indication that 1042141 affects 
librust-kv-log-macro-dev,rust-sequoia-net,rust-futures-timer,rust-async-std-resolver,rust-ahash,rust-trust-dns-resolver,aardvark-dns,rust-async-attributes,rust-ashpd,rust-flume,rust-trust-dns-client,rust-trust-dns-server,rust-erbium,rust-oxilangtag,rust-async-tar,rust-rustls,rust-ahash-0.7,rust-oxiri
Marked as fixed in versions rust-log/0.4.20-2.
Marked as found in versions rust-log/0.4.19-2.
Merged 1040837 1042141
> thanks
Stopping processing here.

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

Processed: retitle 1042499 to ocaml-duppy depends on obsolete pcre ...

[Debian Bug Tracking System]

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

> retitle 1042499 ocaml-duppy depends on obsolete pcre
Bug #1042499 [src:ocaml-duppy] Depends on obsolete pcre
Changed Bug title to 'ocaml-duppy depends on obsolete pcre' from 'Depends on 
obsolete pcre'.
> retitle 1042501 ocsigenserver depends on obsolete pcre
Bug #1042501 [src:ocsigenserver] Depends on obsolete pcre
Changed Bug title to 'ocsigenserver depends on obsolete pcre' from 'Depends on 
obsolete pcre'.
> thanks
Stopping processing here.

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