Bug#1041296: ffmpeg: Undocumented build dependency on libunwind-dev

[Sebastian Ramacher]

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

On 2023-07-16 22:56:32 -0400, Theodoric Stier wrote:
> Source: ffmpeg
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: kerd...@gmail.com
> 
> Dear Maintainer,
> 
> This source package requires the debian package libunwind-dev as a build 
> dependency, but it is not installed by apt-src. This usually means the build 
> dependency needs to be added to the BuildDepends field of the package data.

Looking at some of the last successful build logs, indicates that ffmpeg
builds just fine without libunwind-dev. If you see issues, please
provide a full build log.

Cheers
-- 
Sebastian Ramacher

Processed: Re: Bug#1041296: ffmpeg: Undocumented build dependency on libunwind-dev

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #1041296 [src:ffmpeg] ffmpeg: Undocumented build dependency on libunwind-dev
Added tag(s) moreinfo.
> severity -1 normal
Bug #1041296 [src:ffmpeg] ffmpeg: Undocumented build dependency on libunwind-dev
Severity set to 'normal' from 'serious'

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

Bug#1041302: svt-av1: breaks ABI without SONAME bump

[Sebastian Ramacher]

Source: svt-av1
Version: 1.6.0+dfsg-1
Severity: serious

Version 1.6.0 removed compressed_ten_bit_format from the middle of
EbSvtAv1EncConfiguration, hence changing the memory layout of that
struct. This means that the ABI changed requiring a SONAME bump.

Cheers
-- 
Sebastian Ramacher

Processed: Mark #1037809 as wontfix

[Debian Bug Tracking System]

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

> tags 1037809 + wontfix
Bug #1037809 [src:opm-material] opm-material: ftbfs with GCC-13
Added tag(s) wontfix.
>
End of message, stopping processing here.

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

Bug#1041301: src:drbl: fails to migrate to testing for too long: can't be installed on arm64

[Paul Gevers]

Source: drbl
Version: 5.2.7-1
Severity: serious
Control: close -1 5.2.17-1
Tags: sid trixie
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:drbl has been trying to migrate for 36 
days [2]. Hence, I am filing this bug. drbl has reverse dependencies 
that are currently installable in testing, but would because 
uninstallable if drbl would migrate.


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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:drbl: fails to migrate to testing for too long: can't be installed on arm64

[Debian Bug Tracking System]

Processing control commands:

> close -1 5.2.17-1
Bug #1041301 [src:drbl] src:drbl: fails to migrate to testing for too long: 
can't be installed on arm64
Marked as fixed in versions drbl/5.2.17-1.
Bug #1041301 [src:drbl] src:drbl: fails to migrate to testing for too long: 
can't be installed on arm64
Marked Bug as done

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

Bug#1041026: marked as done (leveldb FTBFS with googletest 1.13.0)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jul 2023 06:06:25 +
with message-id 
and subject line Bug#1041026: fixed in leveldb 1.23-5
has caused the Debian Bug report #1041026,
regarding leveldb FTBFS with googletest 1.13.0
to be marked as done.

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

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


-- 
1041026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: leveldb
Version: 1.23-4
Severity: serious
Tags: ftbfs trixie sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/leveldb.html

...
In file included from /usr/include/gmock/internal/gmock-port.h:57,
 from /usr/include/gmock/internal/gmock-internal-utils.h:49,
 from /usr/include/gmock/gmock-actions.h:145,
 from /usr/include/gmock/gmock.h:56,
 from /build/1st/leveldb-1.23/./util/testutil.h:8,
 from /build/1st/leveldb-1.23/util/testutil.cc:5:
/usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less 
than C++14 are not supported.
  270 | #error C++ versions less than C++14 are not supported.
  |  ^
...


This can be fixed by setting CMAKE_CXX_STANDARD to 14 in CMakeLists.txt.
--- End Message ---
--- Begin Message ---
Source: leveldb
Source-Version: 1.23-5
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated leveldb 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: Mon, 17 Jul 2023 07:05:16 +0200
Source: leveldb
Architecture: source
Version: 1.23-5
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1041026
Changes:
 leveldb (1.23-5) unstable; urgency=medium
 .
   * Configure with C++14 standard (closes: #1041026).
Checksums-Sha1:
 4ec76189fa62fddfea8d1d818a2a56ec47c777c4 2044 leveldb_1.23-5.dsc
 dadf25b63fa4258979a507e11fb5e2cb398443ff 10292 leveldb_1.23-5.debian.tar.xz
Checksums-Sha256:
 c35f84d13e808d9411a6fdfb6189b5e4a6ed411b21b82d4d73da1a051b216f8e 2044 
leveldb_1.23-5.dsc
 727332d7c44372c13dcc1d99e9a9d88e98f16e77aef9b4e76f8dcc6be845665e 10292 
leveldb_1.23-5.debian.tar.xz
Files:
 426ebfec885284e78b9e5869d53bc598 2044 database optional leveldb_1.23-5.dsc
 8fe6e02eac642d5ba3d8cba429852bc6 10292 database optional 
leveldb_1.23-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmS0zrkACgkQ3OMQ54ZM
yL+u5g/+JhYah/OAAE4oiLslb46uyqYXjB9E2cAxF0CNen4oMXQJRlxnjAzdQhzK
sbYQpx/uPL3jAvOU0igmIJQH9ziHttrFK6RT9fRFaH2ca1NnM4utHNI9vxF6Ei15
YzC0KogWfhVqH6hMmeMjzmgzDJZ9HKnZaGAaiYBQLwyr/jS13fEKTLXXmWrSFZwW
dEK3WAE+2wDbl5hZxpI9cy/sqJVyC2SVH6quY5DR4oDIEtK4hFglGwFFEWVcXpVy
3fz9bm5tk8Xds5yaXbeziRmF6qjtQxIv51QeqU33XgA2P9zmqOIV4XyR16LXl3ED
S/8ifeHvEUM1EIWL2z4hvQdz6mtRj7FO4q0OKAhrOWtlhW63fjAuLfak8UtdOC4+
LSpLSGIhQ/qYSU6jDgGk9+yonGPBinobQYYfIvH1Iyl0qjs9rQDWoOxUIqyfRC3F
2CmZqE+kXObE+2KIAb8KTyTsp/gtWkWcTMNZlG5fdtomL0P4fHhk69Um6KSlCKDR
741Crz/uytzuPqUyHekABnjkNsTJwaUTtiE3dx7DNtod3RqZAVD5bCAqrbAyJ47p
SHeXiMOKlFwxt5DRxe8yMkJpQAchEN686ZCZuEPOC9NfoBavggursZowOCc/R6zC
Qyf0lcFAzQsTum5y4V00IeJaP6WhuNoxxyObVu5wiUysHskMBGk=
=H2v/
-END PGP SIGNATURE End Message ---

Processed: bug 1041297 is forwarded to https://github.com/developmentseed/geojson-pydantic/issues/139

[Debian Bug Tracking System]

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

> forwarded 1041297 
> https://github.com/developmentseed/geojson-pydantic/issues/139
Bug #1041297 {Done: Bas Couwenberg } 
[src:geojson-pydantic] geojson-pydantic: autopkgtest failure with GEOS 3.12
Set Bug forwarded-to-address to 
'https://github.com/developmentseed/geojson-pydantic/issues/139'.
> thanks
Stopping processing here.

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

Processed: tagging 1041297

[Debian Bug Tracking System]

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

> tags 1041297 + sid trixie
Bug #1041297 {Done: Bas Couwenberg } 
[src:geojson-pydantic] geojson-pydantic: autopkgtest failure with GEOS 3.12
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Bug#1041300: qt6-base-dev: undeclared file conflict with libqt6opengl6-dev

[Helmut Grohne]

Package: qt6-base-dev
Version: 6.4.2+dfsg-12
Severity: serious

The recent upload makes qt6-base-dev include a fair number of files also
contained in libqt6opengl6-dev. Is this some kind of packaging mistake?

Helmut

Bug#1041299: rawloader: multiple undeclared file conflicts

[Helmut Grohne]

Package: rawloader
Version: 0.37.1-1
Severity: serious

rawloader contains multiple undeclared file conflicts

usr/bin/identify is contained in graphicsmagick-imagemagick-compat.
usr/bin/benchmark is contained in libplucene-perl.

In general, these names are fairly generic. I recommend renaming them
rather than expressing these conflicts. Also adding manual pages would
be good.

Helmut

Processed: tagging 1041297

[Debian Bug Tracking System]

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

> tags 1041297 + ftbfs
Bug #1041297 {Done: Bas Couwenberg } 
[src:geojson-pydantic] geojson-pydantic: autopkgtest failure with GEOS 3.12
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1041297: marked as done (geojson-pydantic: autopkgtest failure with GEOS 3.12)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jul 2023 04:19:04 +
with message-id 
and subject line Bug#1041297: fixed in geojson-pydantic 0.6.3-1
has caused the Debian Bug report #1041297,
regarding geojson-pydantic: autopkgtest failure with GEOS 3.12
to be marked as done.

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

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


-- 
1041297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geojson-pydantic
Version: 0.5.0-2
Severity: serious
Tags: upstream
Justification: autopkgtest failure

Dear Maintainer,

The autopkgtest of your package fails with GEOS 3.12:

 33s === FAILURES 
===
 33s ___ test_multi_point_valid_coordinates[coordinates0] 
___
 33s 
 33s coordinates = [(1.0, 2.0)]
 33s 
 33s @pytest.mark.parametrize(
 33s "coordinates",
 33s [
 33s [(1.0, 2.0)],
 33s [(1.0, 2.0), (1.0, 2.0)],
 33s [(1.0, 2.0, 3.0), (1.0, 2.0, 3.0)],
 33s [(1.0, 2.0), (1.0, 2.0)],
 33s ],
 33s )
 33s def test_multi_point_valid_coordinates(coordinates):
 33s """
 33s Two or three number elements as coordinates shold be okay
 33s """
 33s p = MultiPoint(coordinates=coordinates)
 33s assert p.type == "MultiPoint"
 33s assert p.coordinates == coordinates
 33s assert hasattr(p, "__geo_interface__")
 33s >   assert_wkt_equivalence(p)
 33s 
 33s tests/test_geometries.py:68: 
 33s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ 
 33s 
 33s geom = MultiPoint(type='MultiPoint', coordinates=[(1.0, 2.0)])
 33s 
 33s def assert_wkt_equivalence(geom: Union[Geometry, GeometryCollection]):
 33s """Assert WKT equivalence with Shapely."""
 33s # Remove any trailing `.0` to match Shapely format
 33s clean_wkt = re.sub(r"\.0(\D)", r"\1", geom.wkt)
 33s >   assert shape(geom.dict()).wkt == clean_wkt
 33s E   AssertionError: assert 'MULTIPOINT ((1 2))' == 'MULTIPOINT (1 2)'
 33s E - MULTIPOINT (1 2)
 33s E + MULTIPOINT ((1 2))
 33s E ?+ +
 33s 
 33s tests/test_geometries.py:25: AssertionError
 33s === short test summary info 

 33s FAILED 
tests/test_geometries.py::test_multi_point_valid_coordinates[coordinates0]
 33s !! stopping after 1 failures 
!!!
 33s = 1 failed, 21 passed in 0.30s 
=

https://ci.debian.net/data/autopkgtest/testing/amd64/g/geojson-pydantic/35907622/log.gz
--- End Message ---
--- Begin Message ---
Source: geojson-pydantic
Source-Version: 0.6.3-1
Done: Bas Couwenberg 

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated geojson-pydantic 
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: Mon, 17 Jul 2023 05:56:42 +0200
Source: geojson-pydantic
Architecture: source
Version: 0.6.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Bas Couwenberg 
Closes: 1041297
Changes:
 geojson-pydantic (0.6.3-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
   * Update gbp.conf to use pristine-tar by default.
   * Add patch to fix FTBFS with GEOS 3.12.
 (closes: #1041297)
Checksums-Sha1:
 c6e4a6bb40f4549034d666571293d9ceb16d6488 2265 geojson-pydantic_0.6.3-1.dsc
 3124b0a31c12496a514a6614f4dc78654bea68e1 17283 
geojson-pydantic_0.6.3.orig.tar.gz
 37eb98809599b9405c7334b98f08c93d8c8953d4 2756 
geojson-pydantic_0.6.3-1.debian.tar.xz
 b3d93503569eb6af9e815ed5984a3b9a79ccf9fd 9089 
geojson-pydantic_0.6.3-1_amd64.buildinfo
Checksums-Sha256:
 b8ceafc3416fb57300e8208d6ecbecb0ac9290249d989ff8892c06bb38bbe096 2265 
geojson-pydantic_0.6.3-1.dsc
 94de248b44936ea0580f419d0aecd62abe7324d5474743dc3904c4d32ed6

Bug#1041297: geojson-pydantic: autopkgtest failure with GEOS 3.12

[Bas Couwenberg]

Source: geojson-pydantic
Version: 0.5.0-2
Severity: serious
Tags: upstream
Justification: autopkgtest failure

Dear Maintainer,

The autopkgtest of your package fails with GEOS 3.12:

 33s === FAILURES 
===
 33s ___ test_multi_point_valid_coordinates[coordinates0] 
___
 33s 
 33s coordinates = [(1.0, 2.0)]
 33s 
 33s @pytest.mark.parametrize(
 33s "coordinates",
 33s [
 33s [(1.0, 2.0)],
 33s [(1.0, 2.0), (1.0, 2.0)],
 33s [(1.0, 2.0, 3.0), (1.0, 2.0, 3.0)],
 33s [(1.0, 2.0), (1.0, 2.0)],
 33s ],
 33s )
 33s def test_multi_point_valid_coordinates(coordinates):
 33s """
 33s Two or three number elements as coordinates shold be okay
 33s """
 33s p = MultiPoint(coordinates=coordinates)
 33s assert p.type == "MultiPoint"
 33s assert p.coordinates == coordinates
 33s assert hasattr(p, "__geo_interface__")
 33s >   assert_wkt_equivalence(p)
 33s 
 33s tests/test_geometries.py:68: 
 33s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ 
 33s 
 33s geom = MultiPoint(type='MultiPoint', coordinates=[(1.0, 2.0)])
 33s 
 33s def assert_wkt_equivalence(geom: Union[Geometry, GeometryCollection]):
 33s """Assert WKT equivalence with Shapely."""
 33s # Remove any trailing `.0` to match Shapely format
 33s clean_wkt = re.sub(r"\.0(\D)", r"\1", geom.wkt)
 33s >   assert shape(geom.dict()).wkt == clean_wkt
 33s E   AssertionError: assert 'MULTIPOINT ((1 2))' == 'MULTIPOINT (1 2)'
 33s E - MULTIPOINT (1 2)
 33s E + MULTIPOINT ((1 2))
 33s E ?+ +
 33s 
 33s tests/test_geometries.py:25: AssertionError
 33s === short test summary info 

 33s FAILED 
tests/test_geometries.py::test_multi_point_valid_coordinates[coordinates0]
 33s !! stopping after 1 failures 
!!!
 33s = 1 failed, 21 passed in 0.30s 
=

https://ci.debian.net/data/autopkgtest/testing/amd64/g/geojson-pydantic/35907622/log.gz

Bug#1041296: ffmpeg: Undocumented build dependency on libunwind-dev

[Theodoric Stier]

Source: ffmpeg
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: kerd...@gmail.com

Dear Maintainer,

This source package requires the debian package libunwind-dev as a build 
dependency, but it is not installed by apt-src. This usually means the build 
dependency needs to be added to the BuildDepends field of the package data.

Thanks,
Ted Stier

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

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

-- no debconf information

Bug#1040580: marked as done (oz: implicitly depends on python3-py)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jul 2023 00:22:22 +
with message-id 
and subject line Bug#1040580: fixed in oz 0.17.0-5.2
has caused the Debian Bug report #1040580,
regarding oz: implicitly depends on python3-py
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Dear maintainer,

your package implicitly depends on python3-py for its autopkgtest, which used
to be provided by python3-pytest. However, pytest has dropped that dependency,
breaking your autopkgtest.

Note that you can replace py.test.foo with pytest.foo and avoid the
dependency on python3-py altogether.


Cheers
Timo

- ---

Relevant excerpt from
https://ci.debian.net/data/autopkgtest/testing/amd64/o/oz/35449828/log.gz

 50s  ERRORS 

 50s  ERROR collecting tests/factory/test_factory.py 

 50s tests/factory/test_factory.py:34: in 
 50s import py.test
 50s E   ModuleNotFoundError: No module named 'py.test'; 'py' is not a package
 50s 
 50s During handling of the above exception, another exception occurred:
 50s /usr/lib/python3/dist-packages/_pytest/runner.py:341: in from_call
 50s result: Optional[TResult] = func()
 50s /usr/lib/python3/dist-packages/_pytest/runner.py:372: in 
 50s call = CallInfo.from_call(lambda: list(collector.collect()), "collect")
 50s /usr/lib/python3/dist-packages/_pytest/python.py:531: in collect
 50s self._inject_setup_module_fixture()
 50s /usr/lib/python3/dist-packages/_pytest/python.py:545: in 
_inject_setup_module_fixture
 50s self.obj, ("setUpModule", "setup_module")
 50s /usr/lib/python3/dist-packages/_pytest/python.py:310: in obj
 50s self._obj = obj = self._getobj()
 50s /usr/lib/python3/dist-packages/_pytest/python.py:528: in _getobj
 50s return self._importtestmodule()
 50s /usr/lib/python3/dist-packages/_pytest/python.py:617: in _importtestmodule
 50s mod = import_path(self.path, mode=importmode, 
root=self.config.rootpath)
 50s /usr/lib/python3/dist-packages/_pytest/pathlib.py:565: in import_path
 50s importlib.import_module(module_name)
 50s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 50s return _bootstrap._gcd_import(name[level:], package, level)
 50s :1204: in _gcd_import
 50s ???
 50s :1176: in _find_and_load
 50s ???
 50s :1147: in _find_and_load_unlocked
 50s ???
 50s :690: in _load_unlocked
 50s ???
 50s /usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:178: in 
exec_module
 50s exec(co, module.__dict__)
 50s tests/factory/test_factory.py:37: in 
 50s sys.exit(1)
 50s E   SystemExit: 1
 50s --- Captured stdout 

 50s Unable to import py.test.  Is py.test installed?
 50s __ ERROR collecting tests/guest/test_guest.py 
__
 50s tests/guest/test_guest.py:34: in 
 50s import py.test
 50s E   ModuleNotFoundError: No module named 'py.test'; 'py' is not a package
 50s 
 50s During handling of the above exception, another exception occurred:
 50s /usr/lib/python3/dist-packages/_pytest/runner.py:341: in from_call
 50s result: Optional[TResult] = func()
 50s /usr/lib/python3/dist-packages/_pytest/runner.py:372: in 
 50s call = CallInfo.from_call(lambda: list(collector.collect()), "collect")
 50s /usr/lib/python3/dist-packages/_pytest/python.py:531: in collect
 50s self._inject_setup_module_fixture()
 50s /usr/lib/python3/dist-packages/_pytest/python.py:545: in 
_inject_setup_module_fixture
 50s self.obj, ("setUpModule", "setup_module")
 50s /usr/lib/python3/dist-packages/_pytest/python.py:310: in obj
 50s self._obj = obj = self._getobj()
 50s /usr/lib/python3/dist-packages/_pytest/python.py:528: in _getobj
 50s return self._importtestmodule()
 50s /usr/lib/python3/dist-packages/_pytest/python.py:617: in _importtestmodule
 50s mod = import_path(self.path, mode=importmode, 
root=self.config.rootpath)
 50s /usr/lib/python3/dist-packages/_pytest/pathlib.py:565: in import_path
 50s importlib.import_module(module_name)
 50s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 50s return _bootstrap._gcd_import(name[level:], package, level)
 50s :1204: in _gcd_import
 50s ???
 50s :1176: in _find_and_load
 50s ???
 50s :1147: in _find_and_load_unloc

Bug#1041157: marked as done (Segfault on Rpi1B)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 19:51:23 -0400
with message-id <20230716235123.auvk37rg57hglwlr@localhost>
and subject line Re: Bug#1041157: Segfault on Rpi1B
has caused the Debian Bug report #1041157,
regarding Segfault on Rpi1B
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.)


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

Package: vim-nox
X-Debbugs-Cc: phil...@marek.priv.at
Version: 2:9.0.1672-1
Severity: grave


When running vim on an Rpi1B (which is otherwise stable), vim crashes 
immediately.



# LD_DEBUG=all vim -u none -U none --clean
...
  4400: symbol=_ITM_registerTMCloneTable;  lookup in 
file=/lib/arm-linux-gnueabi/libexpat.so.1 [0]
  4400: symbol=_ITM_registerTMCloneTable;  lookup in 
file=/lib/arm-linux-gnueabi/libgcc_s.so.1 [0]

  4400:
  4400: relocation processing: 
/lib/arm-linux-gnueabi/libruby-3.1.so.3.1 (lazy)

Segmentation fault

Using gdb shows

# gdb --args vim --clean
...
Starting program: /usr/bin/vim

Program received signal SIGSEGV, Segmentation fault.
0xb6fe6378 in elf_dynamic_do_Rel (skip_ifunc=, 
lazy=0, nrelative=0, relsize=0, reladdr=0, scope=, 
map=0xb6fd3ce0) at do-rel.h:53

53  do-rel.h: No such file or directory.
(gdb) bt
#0  0xb6fe6378 in elf_dynamic_do_Rel (skip_ifunc=, 
lazy=0, nrelative=0, relsize=0, reladdr=0, scope=, 
map=0xb6fd3ce0) at do-rel.h:53
#1  _dl_relocate_object (l=l@entry=0xb6fd3ce0, scope=out>, reloc_mode=, consider_profiling=, 
consider_profiling@entry=0) at dl-reloc.c:301
#2  0xb6ff1dec in dl_main (phdr=, phnum=out>, user_entry=, auxv=) at rtld.c:2320
#3  0xb6fee62c in _dl_sysdep_start 
(start_argptr=start_argptr@entry=0xbefff820, dl_main=0xb6ff0268 
) at ../sysdeps/unix/sysv/linux/dl-sysdep.c:140

#4  0xb6fefe0c in _dl_start_final (arg=0xbefff820) at rtld.c:498
#5  _dl_start (arg=0xbefff820) at rtld.c:585
#6  0xb6feed14 in _start () from /lib/ld-linux.so.3
Backtrace stopped: previous frame identical to this frame (corrupt 
stack?)

(gdb) info registers
r0 0xbefff450  3204445264
r1 0x0 0
r2 0x0 0
r3 0x0 0
r4 0xb603d000  3053703168
r5 0x0 0
r6 0x0 0
r7 0xbefff470  3204445296
r8 0x1 1
r9 0xb6fd3ce0  3070049504
r100xb6fffa0c  3070229004
r110xbefff494  3204445332
r120x0 0
sp 0xbefff3f8  0xbefff3f8
lr 0xbefff450  -1090522032
pc 0xb6fe6378  0xb6fe6378 
<_dl_relocate_object+724>

cpsr   0x6010  1610612752
fpscr  0x0 0


Using vim.tiny reports

Error detected while processing /root/.vimrc:
line4:
E319: Sorry, the command is not available in this version: syntax on
Press ENTER or type command to continue

but doesn't crash.


-- Package-specific info:

--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.nox
/usr/bin/vim is /usr/bin/vim.nox

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: armel (armv6l)

Kernel: Linux 6.1.0-9-rpi (UP)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C.UTF-8, LC_CTYPE=C.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

Versions of packages vim-nox depends on:
ii  libacl12.3.1-3
ii  libc6  2.37-5
ii  libgpm21.20.7-10+b1
ii  liblua5.2-05.2.4-3
ii  libperl5.365.36.0-7
ii  libpython3.11  3.11.4-1
ii  libruby3.1 3.1.2-7
ii  libselinux13.4-1+b6
ii  libsodium231.0.18-1
ii  libtcl8.6  8.6.13+dfsg-2
ii  libtinfo6  6.4+20230625-1
ii  vim-common 2:9.0.1672-1
ii  vim-runtime2:9.0.1672-1

vim-nox recommends no packages.

Versions of packages vim-nox suggests:
pn  cscope   
pn  vim-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, Jul 16, 2023 at 01:01:10PM +0200, Philipp Marek wrote:
> Please disregard, SD-card was broken in a few blocks.
> 
> Had no errors in dmesg, but "dpkg --verify" showed a few bad files -
> among then libruby wh

Bug#1041284: marked as done (rust-ureq - please update to support new serde-json)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 23:42:57 +
with message-id 
and subject line Bug#1041284: fixed in rust-ureq 2.7.1-1
has caused the Debian Bug report #1041284,
regarding rust-ureq - please update to support new serde-json
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.)


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

Package: rust-ureq
Version: 2.7.0-1
Severity: serious

Hi.

A change to error reporting in serde_json 1.0.94, intended to prevent
duplicate error messages broke an error-handling code-path in ureq.

ureq's initial fix was to impose an upper limit on the version of
serde_json. Later a proper fix was made by adding a new method
to serde_json::error and changing ureq to use it.

I've just updated serde_json, please update ureq to match.
--- End Message ---
--- Begin Message ---
Source: rust-ureq
Source-Version: 2.7.1-1
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-ureq 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: Mon, 17 Jul 2023 00:38:59 +0200
Source: rust-ureq
Architecture: source
Version: 2.7.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1041284
Changes:
 rust-ureq (2.7.1-1) unstable; urgency=medium
 .
   [ upstream ]
   * new release
 .
   [ Jonas Smedegaard ]
   * bump version for provided virtual packages and autopkgtest hints
   * unfuzz patch 2003
   * tighten (build-)dependencies for crate serde_json;
 closes: bug#1041284, thanks to Peter Green
Checksums-Sha1:
 b63d0829986c17d06461caadbf205b760c0da1b1 3486 rust-ureq_2.7.1-1.dsc
 2bd7cf6409011763dfdbdcf667bb65947595cee8 104545 rust-ureq_2.7.1.orig.tar.gz
 62cc4aed6f7674ce0af45d05bc067a40a476770a 14576 rust-ureq_2.7.1-1.debian.tar.xz
 9e40daa28aa1651295259bbcbf29062c9f26cb63 16354 
rust-ureq_2.7.1-1_amd64.buildinfo
Checksums-Sha256:
 37b1da794ad0de9431ad3a8e47ea478fa0c1a354911ef081baf801b2c87a7fba 3486 
rust-ureq_2.7.1-1.dsc
 c25bd50c86be733da0c3b494c20fc92430e7e52f9dfb1ab90a8b5ed30b9dfda3 104545 
rust-ureq_2.7.1.orig.tar.gz
 18afdce852d1477eef758f0d29ad009698b583d7a455d3cbefe699ac57ecd98f 14576 
rust-ureq_2.7.1-1.debian.tar.xz
 9b0a1408cd59a2deb85fbcdb15d20471e58363d77e07a8d902e4f7b970ac6e54 16354 
rust-ureq_2.7.1-1_amd64.buildinfo
Files:
 9f9cc0dca06592da6204f5eb1c5ecc4a 3486 rust optional rust-ureq_2.7.1-1.dsc
 5b8151e37cc85400a89c65e5dd945fa2 104545 rust optional 
rust-ureq_2.7.1.orig.tar.gz
 1b5ef01bac9e5705e4f78429186d08ca 14576 rust optional 
rust-ureq_2.7.1-1.debian.tar.xz
 234d6888c94055a8da46f37b4c0cb6e5 16354 rust optional 
rust-ureq_2.7.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmS0cmQACgkQLHwxRsGg
ASEA4w//f/fPh9zty+tWDWVIOhvGeJ5gvBgIjyHXV4+2cA2aEjhraiVsoNGZddkh
yq8h4F1sNBtIFFTCgC6iAXt5jnkDP3Cl47YxgGE+KgTdqoExm7Uz/71T5ATlth9O
yzCJ4SDl1Xh5QoSrZwIMKNUMNlSqdkyLuwP0+s6irpt5dBKc23I1FV/YvC6BXcmv
oBE9T8MsvgLnKrEt/hMZvg0yAqNvJM2elIhd8rexMwlYanHu2CxhthOOcUvH2Q07
0/5dtiMNKeZFbg5AHHFcqrFv1imcEhiL9cHfV+Wr1OvSGhi1qA3zxSAPGMcR0k3E
tv95J76H568WCpIIArS/5JXJvd9Cnz6KQ7gRDhfw15fiCSNSDBLIINwL8xWCPr6S
HQwVg4A0B6rQ9/wZs0yV1j3U63spgpgUZtJzK6GHt3Bdt+QZbfdWlJ4Hi3YVd+yN
Ll4M+pa2xgA55uzVqQZcE8IkQBJa3/YZDhTESJ7/vKIncXjd2CtYWflVq/+MRXuk
pejElOu8/9nsluXx25aPnxspfdcIFwCE3/8RoFwoKqgdUm/jVcZ9dFLUAjlnepId
o/qspqX3Q8nPqv48X/Ymb/qKsiUu4njkBiRrWU/KonLo49EtJXRj5LJVV1GOO9QL
Urtkc7xqPm7IzQ+yNxkm/yyPYmTRlA/H7hz9jWQ5h0KLdRFABzU=
=3dSM
-END PGP SIGNATURE End Message ---

Bug#1037738: marked as done (libsecrecy: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 23:38:49 +
with message-id 
and subject line Bug#1037738: fixed in libsecrecy 0.0.5+ds-3
has caused the Debian Bug report #1037738,
regarding libsecrecy: ftbfs with GCC-13
to be marked as done.

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

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


-- 
1037738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libsecrecy
Version: 0.0.5+ds-2
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/libsecrecy_0.0.5+ds-2_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

[...]
  |  ^~~
./libsecrecy/RawKey.hpp: In instantiation of ‘void 
libsecrecy::RawKey<_keysize>::readKey(libsecrecy::GPGMEContext&, std::istream&, 
const libsecrecy::SecrecyKeyValueStore&) [with long unsigned int _keysize = 32; 
std::istream = std::basic_istream]’:
./libsecrecy/GCMFactoryBase.hpp:74:54:   required from here
./libsecrecy/RawKey.hpp:697:62: error: ‘hexToNum’ was not declared in this scope
./libsecrecy/RawKey.hpp:699:62: error: ‘hexToNum’ was not declared in this 
scope, and no declarations were found by argument-dependent lookup at the point 
of instantiation
  699 | uint8_t const low  = hexToNum(*it++) << 
0;
  |  ^~~
./libsecrecy/RawKey.hpp:697:62: note: ‘hexToNum’ declared here, later in the 
translation unit
  697 | uint8_t const high = hexToNum(*it++) << 
4;
  |  ^~~
apps/secrecy.cpp: In function ‘int importKey(const char*, int, char**)’:
apps/secrecy.cpp:265:61: error: ‘hexToNum’ is not a member of 
‘libsecrecy::NumToHex’
  265 | uint8_t const uhigh = 
libsecrecy::NumToHex::hexToNum(hexinput[i++]);
  | ^~~~
apps/secrecy.cpp:266:61: error: ‘hexToNum’ is not a member of 
‘libsecrecy::NumToHex’
  266 | uint8_t const ulow  = 
libsecrecy::NumToHex::hexToNum(hexinput[i++]);
  | ^~~~
apps/secrecy.cpp:319:61: error: ‘hexToNum’ is not a member of 
‘libsecrecy::NumToHex’
  319 | uint8_t const uhigh = 
libsecrecy::NumToHex::hexToNum(shash[2*i+0]);
  | ^~~~
apps/secrecy.cpp:320:60: error: ‘hexToNum’ is not a member of 
‘libsecrecy::NumToHex’
  320 | uint8_t const ulow = 
libsecrecy::NumToHex::hexToNum(shash[2*i+1]);
  |^~~~
apps/secrecy.cpp:344:61: error: ‘hexToNum’ is not a member of 
‘libsecrecy::NumToHex’
  344 | uint8_t const uhigh = 
libsecrecy::NumToHex::hexToNum(c_bindata_a[2*i+0]);
  | ^~~~
apps/secrecy.cpp:345:61: error: ‘hexToNum’ is not a member of 
‘libsecrecy::NumToHex’
  345 | uint8_t const ulow  = 
libsecrecy::NumToHex::hexToNum(c_bindata_a[2*i+1]);
  | ^~~~
./libsecrecy/RawKey.hpp: In instantiation of ‘void 
libsecrecy::RawKey<_keysize>::readKey(libsecrecy::GPGMEContext&, std::istream&, 
const libsecrecy::SecrecyKeyValueStore&) [with long unsigned int _keysize = 16; 
std::is

Processed: oz: diff for NMU version 0.17.0-5.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1040580 + patch
Bug #1040580 [src:oz] oz: implicitly depends on python3-py
Added tag(s) patch.
> tags 1040580 + pending
Bug #1040580 [src:oz] oz: implicitly depends on python3-py
Added tag(s) pending.

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

Bug#1040580: oz: diff for NMU version 0.17.0-5.2

[Timo Röhling]

Control: tags 1040580 + patch
Control: tags 1040580 + pending

Dear maintainer,

I've prepared an NMU for oz (versioned as 0.17.0-5.2) and
uploaded it directly to unstable.


Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯
diff -Nru oz-0.17.0/debian/changelog oz-0.17.0/debian/changelog
--- oz-0.17.0/debian/changelog	2022-05-26 17:24:14.0 +0200
+++ oz-0.17.0/debian/changelog	2023-07-17 01:14:10.0 +0200
@@ -1,3 +1,10 @@
+oz (0.17.0-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Depend on python3-py for autopkgtest (Closes: #1040580)
+
+ -- Timo Röhling   Mon, 17 Jul 2023 01:14:10 +0200
+
 oz (0.17.0-5.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru oz-0.17.0/debian/tests/control oz-0.17.0/debian/tests/control
--- oz-0.17.0/debian/tests/control	2022-05-26 17:24:14.0 +0200
+++ oz-0.17.0/debian/tests/control	2023-07-17 01:14:10.0 +0200
@@ -1,3 +1,3 @@
 Tests: oz
 Architecture: amd64
-Depends: libvirt-daemon, oz, python3-pytest
+Depends: libvirt-daemon, oz, python3-pytest, python3-py


signature.asc
Description: PGP signature

Processed: meson 1.2.0 is out, bumping bug priority

[Debian Bug Tracking System]

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

> severity 1040682 serious
Bug #1040682 [src:colord] FTBFS in colord with meson 1.2.0 rc2
Severity set to 'serious' from 'important'
> severity 1040748 serious
Bug #1040748 [src:pycairo] ftbfs in pycairo with meson 1.2.0 rc2
Severity set to 'serious' from 'important'
> severity 1040753 serious
Bug #1040753 [src:gupnp-tools] FTBFS in gupnp-tools with meson 1.2.0 rc2
Severity set to 'serious' from 'important'
> severity 1040755 serious
Bug #1040755 [src:rygel] ftbfs in rygel with meson 1.2.0 rc2
Severity set to 'serious' from 'important'
> --
Stopping processing here.

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

Bug#1041284: rust-ureq - please update to support new serde-json

[Peter Green]

Package: rust-ureq
Version: 2.7.0-1
Severity: serious

Hi.

A change to error reporting in serde_json 1.0.94, intended to prevent
duplicate error messages broke an error-handling code-path in ureq.

ureq's initial fix was to impose an upper limit on the version of
serde_json. Later a proper fix was made by adding a new method
to serde_json::error and changing ureq to use it.

I've just updated serde_json, please update ureq to match.

Bug#1037738: marked as pending in libsecrecy

[Étienne Mollier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/libsecrecy/-/commit/0a706c7c01cf00a6aa20fd64c13c34ded798c5e4


gcc-13.patch: add: fix ftbfs.

Closes: #1037738


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1037738

Processed: Bug#1037738 marked as pending in libsecrecy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1037738 [src:libsecrecy] libsecrecy: ftbfs with GCC-13
Added tag(s) pending.

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

Processed: severity of 1041145 is normal

[Debian Bug Tracking System]

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

> severity 1041145 normal
Bug #1041145 [src:firmware-free] firmware-free: Non-debian build dependency 
linux-support (= 5.4.0-3) prevents local revision build.
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: tagging 1041203

[Debian Bug Tracking System]

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

> tags 1041203 + sid trixie
Bug #1041203 [src:macs] FTBFS: InvalidRequirement: Expected end or semicolon
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Bug#1037755: marked as done (linphone: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 20:52:23 +
with message-id 
and subject line Bug#1037755: fixed in linphone 5.2.0-3
has caused the Debian Bug report #1037755,
regarding linphone: ftbfs with GCC-13
to be marked as done.

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

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


-- 
1037755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linphone
Version: 5.1.65-4
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/linphone_5.1.65-4_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

[...]
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
-DBCTBX_LOG_DOMAIN=\"liblinphone\" -DBCTBX_STATIC -DBUILD_LDAP -DHAVE_CONFIG_H 
-DLDAP_ENABLED -DLDAP_LIBS_DYNAMIC -DLINPHONE_EXPORTS -DVCARD_ENABLED 
-DVIDEO_ENABLED -Dlinphone_EXPORTS -I/<>/coreapi 
-I/<>/include -I/<>/src 
-I/<>/obj-x86_64-linux-gnu 
-I/<>/obj-x86_64-linux-gnu/coreapi -I/usr/include/OpenGL 
-I/usr/include/xsd -I/usr/include/libxml2 -isystem /usr/include/belle-sip -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DPACKAGE_SOUND_DIR="\"/usr/share/sounds/linphone\"" 
-DPACKAGE_RING_DIR="\"/usr/share/sounds/linphone/rings\"" -Wdate-time 
-D_FORTIFY_SOURCE=2 -DDEBPATCH_LDAP_HOSTNAME_OVERRIDE=1 -fPIC -std=c++14  -Wall 
-Wconversion -Werror=return-type -Winit-self -Wno-error=deprecated-declarations 
-Wpointer-arith -Wuninitialized -Wunused -Werror -Wextra -Wno-unused-parameter 
-Wno-missing-field-initializ
 ers -fno-strict-aliasing -Wnon-virtual-dtor -Woverloaded-virtual 
-Wsuggest-override -Wno-error=suggest-override -MD -MT 
src/CMakeFiles/linphone.dir/chat/chat-message/notification-message.cpp.o -MF 
CMakeFiles/linphone.dir/chat/chat-message/notification-message.cpp.o.d -o 
CMakeFiles/linphone.dir/chat/chat-message/notification-message.cpp.o -c 
/<>/src/chat/chat-message/notification-message.cpp
[ 35%] Building CXX object 
src/CMakeFiles/linphone.dir/chat/chat-room/abstract-chat-room.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
-DBCTBX_LOG_DOMAIN=\"liblinphone\" -DBCTBX_STATIC -DBUILD_LDAP -DHAVE_CONFIG_H 
-DLDAP_ENABLED -DLDAP_LIBS_DYNAMIC -DLINPHONE_EXPORTS -DVCARD_ENABLED 
-DVIDEO_ENABLED -Dlinphone_EXPORTS -I/<>/coreapi 
-I/<>/include -I/<>/src 
-I/<>/obj-x86_64-linux-gnu 
-I/<>/obj-x86_64-linux-gnu/coreapi -I/usr/include/OpenGL 
-I/usr/include/xsd -I/usr/include/libxml2 -isystem /usr/include/belle-sip -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DPACKAGE_SOUND_DIR="\"/usr/share/sounds/linphone\"" 
-DPACKAGE_RING_DIR="\"/usr/share/sounds/linphone/rings\"" -Wdate-time 
-D_FORTIFY_SOURCE=2 -DDEBPATCH_LDAP_HOSTNAME_OVERRIDE=1 -fPIC -std=c++14  -Wall 
-Wconversion -Werror=return-type -Winit-self -Wno-error=deprecated-declarations 
-Wpointer-arith -Wuninitialized -Wunused -Werror -Wextra -Wno-unused-parameter 
-Wno-missing-field-initializ
 ers -fno-strict-aliasing -Wnon-virtual-dtor -Woverloaded-virtual 
-Wsuggest-override -Wno-error=suggest-override -MD -MT 
src/CMakeFiles/linphone.dir/chat/chat-room/abstract-chat-room.cpp.o -MF 
CMakeFiles/linphone.dir/chat/chat-room/abstract-chat-room.cpp.o.d -o 
CMakeFiles/linphone.dir/chat/chat-room/abstract-chat-room.cpp.o -c 
/<>/src/chat/chat-room/abstract-chat-room.cpp
[ 35%] Building CXX object 
src/CMakeFiles/linphone.dir/chat/chat-room/basic-chat-room.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
-DBCTBX_LOG_DOMAIN=\"liblinphone\" -DBCTBX_STATIC -DBUI

Bug#1041255: marked as done (librubberband-dev: missing dependency on libfftw3-dev)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 20:55:42 +
with message-id 
and subject line Bug#1041255: fixed in rubberband 3.2.1+dfsg-6
has caused the Debian Bug report #1041255,
regarding librubberband-dev: missing dependency on libfftw3-dev
to be marked as done.

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

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


-- 
1041255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librubberband-dev
Version: 3.2.1+dfsg-5
Severity: serious
Control: affects -1 src:ffmpeg

$ pkgconf --modversion rubberband
Package fftw3 was not found in the pkg-config search path.
Perhaps you should add the directory containing `fftw3.pc'
to the PKG_CONFIG_PATH environment variable
Package 'fftw3', required by 'rubberband', not found

This issue causes ffmpeg to FTBFS. Please add the missing dependency on
libfftw3-dev.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: rubberband
Source-Version: 3.2.1+dfsg-6
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated rubberband 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Jul 2023 22:21:30 +0200
Source: rubberband
Architecture: source
Version: 3.2.1+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 1041255
Changes:
 rubberband (3.2.1+dfsg-6) unstable; urgency=medium
 .
   * debian/control: Add dependency on libfftw3-dev (Closes: #1041255)
Checksums-Sha1:
 713d131a4275196ea814c417da1cfd9b14e6f61f 1984 rubberband_3.2.1+dfsg-6.dsc
 d1d52cb2026e82cbb0643496f06afa3397dac44f 12564 
rubberband_3.2.1+dfsg-6.debian.tar.xz
Checksums-Sha256:
 450269166f4ea07090d32309c007d7c02c774a589b59389ce8b8267fe7f36605 1984 
rubberband_3.2.1+dfsg-6.dsc
 1e892920ec437d4c9d330e0030f6fb9adfc9cc3ec7d7e1394b4cda13de0d5cbd 12564 
rubberband_3.2.1+dfsg-6.debian.tar.xz
Files:
 cd6e8e66ba247e157193c0e944c36968 1984 sound optional 
rubberband_3.2.1+dfsg-6.dsc
 da569ed7c02768ca654c32b6a782c2bd 12564 sound optional 
rubberband_3.2.1+dfsg-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZLRSAwAKCRAhk2s2YA/N
ie1qAQD0BOHxmKcI23kezRy66umPPhmMTgJpWTWnyMlVTDwYJAD+Kd71ZINYpMTA
bf98wPZhcdqqzarwoR3c4iHyWvuGOAg=
=uUPr
-END PGP SIGNATURE End Message ---

Bug#1037753: marked as done (lime: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 20:52:07 +
with message-id 
and subject line Bug#1037753: fixed in lime 5.2.0+dfsg-2
has caused the Debian Bug report #1037753,
regarding lime: ftbfs with GCC-13
to be marked as done.

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

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


-- 
1037753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lime
Version: 5.1.64+dfsg-2
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/lime_5.1.64+dfsg-2_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

[...]
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
make  -f CMakeFiles/Makefile2 lime
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
/<>/obj-x86_64-linux-gnu/CMakeFiles 11
make  -f CMakeFiles/Makefile2 src/CMakeFiles/lime.dir/all
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f src/CMakeFiles/lime.dir/build.make src/CMakeFiles/lime.dir/depend
make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/src 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/src 
/<>/obj-x86_64-linux-gnu/src/CMakeFiles/lime.dir/DependInfo.cmake 
--color=
make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f src/CMakeFiles/lime.dir/build.make src/CMakeFiles/lime.dir/build
make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 27%] Building CXX object src/CMakeFiles/lime.dir/lime_x3dh_protocol.cpp.o
[ 27%] Building CXX object src/CMakeFiles/lime.dir/lime_x3dh.cpp.o
[ 27%] Building CXX object src/CMakeFiles/lime.dir/lime.cpp.o
[ 36%] Building CXX object src/CMakeFiles/lime.dir/lime_localStorage.cpp.o
[ 45%] Building CXX object 
src/CMakeFiles/lime.dir/lime_double_ratchet_protocol.cpp.o
[ 54%] Building CXX object src/CMakeFiles/lime.dir/lime_manager.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DBCTBX_STATIC 
-DEC25519_ENABLED -DEC448_ENABLED -DFFI_ENABLED -DLIME_EXPORTS -Dlime_EXPORTS 
-I/<>/include -I/<>/src 
-I/<>/obj-x86_64-linux-gnu -I/usr/include/soci 
-I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -std=gnu++14  
-Wall -Wuninitialized -Wno-deprecated-declarations 
-Wno-missing-field-initializers -Werror -Wextra -Wno-unused-parameter 
-fno-strict-aliasing -MD -MT src/CMakeFiles/lime.dir/lime_x3dh.cpp.o -MF 
CMakeFiles/lime.dir/lime_x3dh.cpp.o.d -o CMakeFiles/lime.dir/lime_x3dh.cpp.o -c 
/<>/src/lime_x3dh.cpp
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DBCTBX_STATIC 
-DEC25519_ENABLED -DEC448_ENABLED -DFFI_ENABLED -DLIME_EXPORTS -Dlime_EXPORTS 
-I/<>/include -I/<>/src 
-I/<>/obj-x86_64-linux-gnu -I/usr/include/soci 
-I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -std=gnu++14  
-Wall -Wuninitialized -Wno-deprecated-declarations 
-Wno-missing-field-initializers -Werror -Wextra -Wno-unused-parameter 
-fno-strict-aliasing -MD -MT src/CMakeFiles/lime.dir/lime.cpp.o -MF 
CMakeFiles/lime.dir/lime.cpp.o.d -o CMakeFiles/lime.dir/lime.cpp.o -c 
/<>/src/lime.cpp
cd /<>/ob

Processed: bug 1040998 is forwarded to https://github.com/acoustid/chromaprint/issues/132

[Debian Bug Tracking System]

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

> forwarded 1040998 https://github.com/acoustid/chromaprint/issues/132
Bug #1040998 [src:chromaprint] chromaprint FTBFS with googletest 1.13.0
Set Bug forwarded-to-address to 
'https://github.com/acoustid/chromaprint/issues/132'.
> thanks
Stopping processing here.

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

Bug#1041271: maildir-utils: public shared library shipped in maildir-utils binary package

[Jeremy Sowden]

On 2023-07-16, at 20:11:30 +0100, Jeremy Sowden wrote:
> On 2023-07-16, at 13:59:43 -0300, David Bremner wrote:
> > I think that libguile-mu.* need to be either moved to a private
> > directory or to their own packages. I don't know enough about guile to
> > say which is better.
> 
> I think it probably wants to go into Guile's extensions directory:
> /usr/lib/${DEB_HOST_MULTIARCH}/guile-3.0/extensions.
> 
> For 1.8, I believe that will require something along the lines of:
> 
>   diff --git a/configure.ac b/configure.ac
>   index 5e44d5d168f9..f99a5cf5c169 100644
>   --- a/configure.ac
>   +++ b/configure.ac
>   @@ -211,6 +211,7 @@ AS_IF([test "x$enable_guile" != "xno"],[
>  GUILE_PKG([3.0 2.2])
>  GUILE_PROGS
>  GUILE_FLAGS
>   +  GUILE_SITE_DIR
>  AC_DEFINE_UNQUOTED([GUILE_BINARY],"$GUILE",[guile binary])
>  vsnarf=guile-snarf${GUILE_EFFECTIVE_VERSION}
>  AC_CHECK_PROGS(GUILE_SNARF,[${vsnarf} guile-snarf], [no])
>   diff --git a/guile/Makefile.am b/guile/Makefile.am
>   index dd911087ded7..992e929c1fdc 100644
>   --- a/guile/Makefile.am
>   +++ b/guile/Makefile.am
>   @@ -42,7 +42,8 @@ AM_CXXFLAGS=  \
>   -Wno-missing-declarations   \
>   -Wno-suggest-attribute=noreturn
>
>   -lib_LTLIBRARIES=   \
>   +guile_extensionsdir = $(GUILE_EXTENSION)
>   +guile_extensions_LTLIBRARIES = \
>   libguile-mu.la
>
>libguile_mu_la_SOURCES=\
> 
> I'll create another MR once I've tested it.

https://salsa.debian.org/emacsen-team/maildir-utils/-/merge_requests/3

J.


signature.asc
Description: PGP signature

Processed: Re: Bug#1040871: reportbug fails to start

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 pysimplesoap 1.16.2-4
Bug #1040871 [reportbug] reportbug fails to start
Bug reassigned from package 'reportbug' to 'pysimplesoap'.
No longer marked as found in versions reportbug/12.0.0.
Ignoring request to alter fixed versions of bug #1040871 to the same values 
previously set
Bug #1040871 [pysimplesoap] reportbug fails to start
There is no source info for the package 'pysimplesoap' at version '1.16.2-4' 
with architecture ''
Unable to make a source version for version '1.16.2-4'
Marked as found in versions 1.16.2-4.
> close -1 1.16.2-5
Bug #1040871 [pysimplesoap] reportbug fails to start
There is no source info for the package 'pysimplesoap' at version '1.16.2-5' 
with architecture ''
Unable to make a source version for version '1.16.2-5'
Marked as fixed in versions 1.16.2-5.
Bug #1040871 [pysimplesoap] reportbug fails to start
Marked Bug as done

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

Bug#1040871: reportbug fails to start

[Sebastian Ramacher]

Control: reassign -1 pysimplesoap 1.16.2-4
Control: close -1 1.16.2-5

On 2023-07-11 21:27:34 +0200, Laurent Martelli wrote:
> Package: reportbug
> Version: 12.0.0
> Severity: grave
> 
> Reportbug fails to start. It seems to relate to the removal of a deprecated
> function in python 3.11.
> 
> Traceback (most recent call last):
>   File "/usr/bin/reportbug", line 40, in 
> from reportbug import utils
>   File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 70, in
> 
> from . import debbugs   # noqa: E402
> ^
>   File "/usr/lib/python3/dist-packages/reportbug/debbugs.py", line 33, in
> 
> import debianbts
>   File "/usr/lib/python3/dist-packages/debianbts/__init__.py", line 1, in
> 
> from debianbts.debianbts import *  # noqa
> ^
>   File "/usr/lib/python3/dist-packages/debianbts/debianbts.py", line 22, in
> 
> from pysimplesoap.client import SoapClient
>   File "/usr/lib/python3/dist-packages/pysimplesoap/__init__.py", line 16,
> in 
> from . import client, server, simplexml, transport
>   File "/usr/lib/python3/dist-packages/pysimplesoap/client.py", line 33, in
> 
> from .transport import get_http_wrapper, set_http_wrapper, get_Http
>   File "/usr/lib/python3/dist-packages/pysimplesoap/transport.py", line
> 109, in 
> if 'timeout' in inspect.getargspec(httplib2.Http.__init__)[0]:
> ^^
> AttributeError: module 'inspect' has no attribute 'getargspec'. Did you
> mean: 'getargs'?

That was fixed in pysimplesoap 1.16.2-5 which is included in bookworm.
This looks like you did not fully upgrade your system to bookworm.

Reassinging and closing.

Cheers
-- 
Sebastian Ramacher

Processed: tagging 1041252, tagging 1040473

[Debian Bug Tracking System]

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

> tags 1041252 + sid trixie
Bug #1041252 {Done: Patrick Franz } [src:libksysguard] 
libksysguard: stop depending on qtwebengine5-dev on mipsel
Added tag(s) sid and trixie.
> tags 1040473 + sid trixie
Bug #1040473 [src:python-click] python-click: FTBFS after new pytest
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Processed: tagging 1040473

[Debian Bug Tracking System]

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

> tags 1040473 + ftbfs
Bug #1040473 [src:python-click] python-click: FTBFS after new pytest
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1041255: marked as pending in rubberband

[Sebastian Ramacher]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/rubberband/-/commit/4147a89d612940a2fd2dd49f72c44da2ed010265


Add dependency on libfftw3-dev

Closes: #1041255


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1041255

Processed: Bug#1041255 marked as pending in rubberband

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1041255 [librubberband-dev] librubberband-dev: missing dependency on 
libfftw3-dev
Added tag(s) pending.

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

Bug#1040412: marked as done (django-q: implicitly depends on python3-pkg-resources)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 19:49:16 +
with message-id 
and subject line Bug#1040412: fixed in django-q 1.3.9-5
has caused the Debian Bug report #1040412,
regarding django-q: implicitly depends on python3-pkg-resources
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

your package implicitly depends on python3-pkg-resources for its autopkgtest, 
which used
to be provided by python3-pytest. However, pytest has dropped that dependency,
breaking your autopkgtest and possibly your package.


Cheers
Timo


Relevant excerpt from
https://ci.debian.net/data/autopkgtest/testing/amd64/d/django-q/35335654/log.gz

 29s autopkgtest [13:19:54]: test python3-django-q: [---
 30s Traceback (most recent call last):
 30s   File "", line 198, in _run_module_as_main
 30s   File "", line 88, in _run_code
 30s   File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 5, in 

 30s raise SystemExit(pytest.console_main())
 30s  ^
 30s   File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 
189, in console_main
 30s code = main()
 30s^^
 30s   File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 
147, in main
 30s config = _prepareconfig(args, plugins)
 30s  ^
 30s   File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 
328, in _prepareconfig
 30s config = pluginmanager.hook.pytest_cmdline_parse(
 30s  
 30s   File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265, in 
__call__
 30s return self._hookexec(self.name, self.get_hookimpls(), kwargs, 
firstresult)
 30s

 30s   File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80, in 
_hookexec
 30s return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
 30s^
 30s   File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 55, in 
_multicall
 30s gen.send(outcome)
 30s   File "/usr/lib/python3/dist-packages/_pytest/helpconfig.py", line 103, 
in pytest_cmdline_parse
 30s config: Config = outcome.get_result()
 30s  
 30s   File "/usr/lib/python3/dist-packages/pluggy/_result.py", line 60, in 
get_result
 30s raise ex[1].with_traceback(ex[2])
 30s   File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39, in 
_multicall
 30s res = hook_impl.function(*args)
 30s   ^
 30s   File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 
1075, in pytest_cmdline_parse
 30s self.parse(args)
 30s   File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 
1425, in parse
 30s self._preparse(args, addopts=addopts)
 30s   File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 
1327, in _preparse
 30s self.hook.pytest_load_initial_conftests(
 30s   File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265, in 
__call__
 30s return self._hookexec(self.name, self.get_hookimpls(), kwargs, 
firstresult)
 30s

 30s   File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80, in 
_hookexec
 30s return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
 30s^
 30s   File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 60, in 
_multicall
 30s return outcome.get_result()
 30s
 30s   File "/usr/lib/python3/dist-packages/pluggy/_result.py", line 60, in 
get_result
 30s raise ex[1].with_traceback(ex[2])
 30s   File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39, in 
_multicall
 30s res = hook_impl.function(*args)
 30s   ^
 30s   File "/usr/lib/python3/dist-packages/pytest_django/plugin.py", line 353, 
in pytest_load_initial_conftests
 30s _setup_django()
 30s   File "/usr/lib/python3/dist-packages/pytest_django/plugin.py", line 236, 
in _setup_django
 30s django.setup()
 30s   File "

Processed: Bug#1040412 marked as pending in django-q

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040412 [src:django-q] django-q: implicitly depends on 
python3-pkg-resources
Added tag(s) pending.

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

Bug#1040412: marked as pending in django-q

[Timo Röhling]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/django-q/-/commit/a20c4f94b2ae328407e0da3388f0444e401d146a


Add test-depend on python3-pkg-resources

Closes: #1040412


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040412

Bug#1041271: maildir-utils: public shared library shipped in maildir-utils binary package

[Jeremy Sowden]

On 2023-07-16, at 13:59:43 -0300, David Bremner wrote:
> Package: maildir-utils
> Version: 1.8.14-2
> Severity: serious
> Justification: violates policy 8.1
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> I think that libguile-mu.* need to be either moved to a private
> directory or to their own packages. I don't know enough about guile to
> say which is better.

I think it probably wants to go into Guile's extensions directory:
/usr/lib/${DEB_HOST_MULTIARCH}/guile-3.0/extensions.

For 1.8, I believe that will require something along the lines of:

  diff --git a/configure.ac b/configure.ac
  index 5e44d5d168f9..f99a5cf5c169 100644
  --- a/configure.ac
  +++ b/configure.ac
  @@ -211,6 +211,7 @@ AS_IF([test "x$enable_guile" != "xno"],[
 GUILE_PKG([3.0 2.2])
 GUILE_PROGS
 GUILE_FLAGS
  +  GUILE_SITE_DIR
 AC_DEFINE_UNQUOTED([GUILE_BINARY],"$GUILE",[guile binary])
 vsnarf=guile-snarf${GUILE_EFFECTIVE_VERSION}
 AC_CHECK_PROGS(GUILE_SNARF,[${vsnarf} guile-snarf], [no])
  diff --git a/guile/Makefile.am b/guile/Makefile.am
  index dd911087ded7..992e929c1fdc 100644
  --- a/guile/Makefile.am
  +++ b/guile/Makefile.am
  @@ -42,7 +42,8 @@ AM_CXXFLAGS=  \
  -Wno-missing-declarations   \
  -Wno-suggest-attribute=noreturn
   
  -lib_LTLIBRARIES=   \
  +guile_extensionsdir = $(GUILE_EXTENSION)
  +guile_extensions_LTLIBRARIES = \
  libguile-mu.la
   
   libguile_mu_la_SOURCES=\

I'll create another MR once I've tested it.

J.


signature.asc
Description: PGP signature

Bug#1040568: marked as done (weresync: implicitly depends on python3-py)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 19:04:12 +
with message-id 
and subject line Bug#1040568: fixed in weresync 1.0.9-3
has caused the Debian Bug report #1040568,
regarding weresync: implicitly depends on python3-py
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Dear maintainer,

your package implicitly depends on python3-py for its autopkgtest, which used
to be provided by python3-pytest. However, pytest has dropped that dependency,
breaking your autopkgtest.

Note that you can replace py.test.foo with pytest.foo to avoid a
dependency on python3-py altogether.


Cheers
Timo


Relevant excerpt from
https://ci.debian.net/data/autopkgtest/testing/amd64/w/weresync/35454503/log.gz

 24s autopkgtest [16:48:55]: test main: [---
 24s Traceback (most recent call last):
 24s   File 
"/tmp/autopkgtest-lxc.ypwky37d/downtmp/build.9Em/src/debian/tests/main", line 
4, in 
 24s py.test.cmdline.main()
 24s ^^^
 24s AttributeError: module 'py' has no attribute 'test'
 24s autopkgtest [16:48:55]: test main: ---]
 25s autopkgtest [16:48:56]: test main:  - - - - - - - - - - results - - - - - 
- - - - -
 25s main FAIL non-zero exit status 1
 25s autopkgtest [16:48:56]: test main:  - - - - - - - - - - stderr - - - - - - 
- - - -
 25s Traceback (most recent call last):
 25s   File 
"/tmp/autopkgtest-lxc.ypwky37d/downtmp/build.9Em/src/debian/tests/main", line 
4, in 
 25s py.test.cmdline.main()
 25s ^^^
 25s AttributeError: module 'py' has no attribute 'test'
 25s autopkgtest [16:48:56]:  summary
 25s main FAIL non-zero exit status 1


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmSoTK0ACgkQ+C8H+466
LVl5TwwAj+0qd9bKB3+/kZsBSL0nfVxCosZRPQfC/FiTTZmeA4cVs1Kc2lmp1k3T
3K6JXCAO9gNLlAfeewTi8gK1h6yPQgUV6RFgFVEj3k9jZazvg5lTLGMhN7m4iE6w
pctwAq7I8Ijf3Xe3YXmWEpzL84RkEjtskRm+FEqc8wmSUYeeMjPTtJjM4M1QpLfa
xxdOzfFiww/Y+xmbrjm9ENQbW94jeoqQ3/paLasrBGZhf0+MLNHsVNFg+LpcXdzv
zg5U+zOLWyGio//l6LYF8rPE4s607bHfPGGHQRA8gbYhPVa6En49B+/U/Iv1patw
mW0iM8J66IBLkVhRELBQ0Crqm9hoPxSzzEB+2Hm4FU1neXsTfBvG1R0+kDrPXSev
Qnvzf1bGH26Gcy8w5Y5Kz/m5D9U5KDrjOrWxpY63gA4FcAhtoDvmjG4K3n/YBdrA
en3eCgUpaKCVMbztxkk+W9wEIIazEiWwbA5uTnx4wVP5Q9lUIwXmt3wKGl1NEBPW
wAChb6EQ
=tWmj
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: weresync
Source-Version: 1.0.9-3
Done: Timo Röhling 

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

Debian distribution maintenance software
pp.
Timo Röhling  (supplier of updated weresync package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Jul 2023 20:36:42 +0200
Source: weresync
Architecture: source
Version: 1.0.9-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Timo Röhling 
Closes: 1040568
Changes:
 weresync (1.0.9-3) unstable; urgency=medium
 .
   * Team upload.
   * Test-depend on e2fsprogs
   * Use pytest, not py.test (Closes: #1040568)
Checksums-Sha1:
 3783761ccf0334dcd376998fd5536092eeac0f2f 2074 weresync_1.0.9-3.dsc
 fab9ab6edeeb243976f7380ae8459e4b079d72ae 7604 weresync_1.0.9-3.debian.tar.xz
 90f268119bf61d17802a94cdc98c7a1353dcadd5 7951 weresync_1.0.9-3_amd64.buildinfo
Checksums-Sha256:
 2e49f9ab0f62368a01f29681e0bc50ef9797af0ffa99ff9ee953b80342594083 2074 
weresync_1.0.9-3.dsc
 aa12d6b8b7b2f3772aa308669a73a062ffb7f771ff0cd3789417d315683fa408 7604 
weresync_1.0.9-3.debian.tar.xz
 a08caf982b6808a1f99063f7aca5913d07395d13d95455bdf118cac64f24418b 7951 
weresync_1.0.9-3_amd64.buildinfo
Files:
 f3d5c0f23a3db1ddb4974b313262aabe 2074 admin optional weresync_1.0.9-3.dsc
 10c23688bbc62497dd0e63666f8c27ca 7604 admin optional 
weresync_1.0.9-3.debian.tar.xz
 a47493f606c99e18953f3ccec190b288 7951 admin optional 
weresync_1.0.

Bug#1040424: marked as done (python-pytest-random-order: implicitly depends on python3-py)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 18:58:51 +
with message-id 
and subject line Bug#1040424: fixed in python-pytest-random-order 1.1.0-2
has caused the Debian Bug report #1040424,
regarding python-pytest-random-order: implicitly depends on python3-py
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.)


-- 
1040424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pytest-random-order
Version: 1.1.0-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

your package implicitly depends on python3-py for its autopkgtest, which used
to be provided by python3-pytest. However, pytest has dropped that dependency,
breaking your autopkgtest and possibly your package.


Cheers
Timo

Relevant excerpt from
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pytest-random-order/35336221/log.gz

 40s  ERRORS 

 40s _ ERROR at setup of test_it_works_with_actual_tests[class-2-5] 
_
 40s 
 40s testdir = 
 40s 
 40s @pytest.fixture
 40s def tmp_tree_of_tests(testdir):
 40s """
 40s Creates a directory structure:
 40s tmpdir/
 40s shallow_tests/
 40s test_a.py 2 passing, 1 failing
 40s deep_tests/
 40s test_b.py 2 passing, 1 failing
 40s test_c.py 1 passing
 40s test_d.py 2 passing
 40s test_e.py a class, 2 passing, 1 failing
 40s 
 40s If module name doesn't start with "test_", it isn't picked up by 
runpytest.
 40s """
 40s 
 40s sup = testdir.mkpydir('shallow_tests')
 40s 
 40s >   sup.join('test_a.py').write(py.code.Source("""
 40s def test_a1():
 40s assert False
 40s def test_a2():
 40s assert True
 40s def test_a3():
 40s assert True
 40s """))
 40s E   AttributeError: module 'py' has no attribute 'code'
 40s 
 40s 
/tmp/autopkgtest-lxc.hl72zszt/downtmp/build.oRr/src/tests/test_actual_test_runs.py:27:
 AttributeError
 40s  ERROR at setup of test_it_works_with_actual_tests[module-2-5] 
_
 40s 
 40s testdir = 
 40s 
 40s @pytest.fixture
 40s def tmp_tree_of_tests(testdir):
 40s """
 40s Creates a directory structure:
 40s tmpdir/
 40s shallow_tests/
 40s test_a.py 2 passing, 1 failing
 40s deep_tests/
 40s test_b.py 2 passing, 1 failing
 40s test_c.py 1 passing
 40s test_d.py 2 passing
 40s test_e.py a class, 2 passing, 1 failing
 40s 
 40s If module name doesn't start with "test_", it isn't picked up by 
runpytest.
 40s """
 40s 
 40s sup = testdir.mkpydir('shallow_tests')
 40s 
 40s >   sup.join('test_a.py').write(py.code.Source("""
 40s def test_a1():
 40s assert False
 40s def test_a2():
 40s assert True
 40s def test_a3():
 40s assert True
 40s """))
 40s E   AttributeError: module 'py' has no attribute 'code'
 40s 
 40s 
/tmp/autopkgtest-lxc.hl72zszt/downtmp/build.oRr/src/tests/test_actual_test_runs.py:27:
 AttributeError
 40s  ERROR at setup of test_it_works_with_actual_tests[package-2-5] 

 40s 
 40s testdir = 
 40s 
 40s @pytest.fixture
 40s def tmp_tree_of_tests(testdir):
 40s """
 40s Creates a directory structure:
 40s tmpdir/
 40s shallow_tests/
 40s test_a.py 2 passing, 1 failing
 40s deep_tests/
 40s test_b.py 2 passing, 1 failing
 40s test_c.py 1 passing
 40s test_d.py 2 passing
 40s test_e.py a class, 2 passing, 1 failing
 40s 
 40s If module name doesn't start with "test_", it isn't picked up by 
runpytest.
 40s """
 40s 
 40s sup = testdir.mkpydir('shallow_tests')
 40s 
 40s >   sup.join('test_a.py').write(py.code.Source("""
 40s def test_a1():
 40s assert False
 40s def test_a2():
 40s assert True
 40s def test_a3():
 40s   

Bug#1040571: marked as done (segno: implicitly depends on python3-pkg-resources)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 19:00:56 +
with message-id 
and subject line Bug#1040571: fixed in segno 1.5.2-3
has caused the Debian Bug report #1040571,
regarding segno: implicitly depends on python3-pkg-resources
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Dear maintainer,

your package implicitly depends on python3-pkg-resources for its autopkgtest,
which used to be provided through python3-pytest. However, pytest has dropped
that dependency, breaking your autopkgtest and possibly your package.

Note that pkg_resources is deprecated in favor of importlib.resources [1],
which is part of the Python Standard Library and has better performance.

Cheers
Timo

[1] https://docs.python.org/3/library/importlib.resources.html

- ---

Relevant excerpt from
https://ci.debian.net/data/autopkgtest/testing/amd64/s/segno/35454502/log.gz

 17s  ERRORS 

 17s ___ ERROR collecting test_plugin.py 

 17s ImportError while importing test module 
'/tmp/autopkgtest-lxc.83hwvtoe/downtmp/autopkgtest_tmp/tests/test_plugin.py'.
 17s Hint: make sure your test modules/packages have valid Python names.
 17s Traceback:
 17s /usr/lib/python3/dist-packages/_pytest/python.py:617: in _importtestmodule
 17s mod = import_path(self.path, mode=importmode, 
root=self.config.rootpath)
 17s /usr/lib/python3/dist-packages/_pytest/pathlib.py:565: in import_path
 17s importlib.import_module(module_name)
 17s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 17s return _bootstrap._gcd_import(name[level:], package, level)
 17s :1204: in _gcd_import
 17s ???
 17s :1176: in _find_and_load
 17s ???
 17s :1147: in _find_and_load_unlocked
 17s ???
 17s :690: in _load_unlocked
 17s ???
 17s /usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:178: in 
exec_module
 17s exec(co, module.__dict__)
 17s test_plugin.py:13: in 
 17s import pkg_resources
 17s E   ModuleNotFoundError: No module named 'pkg_resources'


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmSoTmIACgkQ+C8H+466
LVlu4QwAmsq5VA66wZS6FW39j4G1914q62JgYiqAVU2fWkkK6NjMIRamOyzjn5fS
tj6crNVc5gTWS86PM3uHk895caanjUsuv7lGQeoFcRC5EW5WpTff2v5cCLQM7xIN
yaQasX3pEPlJkawD8DMjLXYmNoL5cpC+uJTObLgS5aKSNfFryKpKRqgeDKQTHIzF
mvwTx8iMQEad6Jp3kDtaFL8Aa4Rvz/BnK8Q50cyr3ien4FnbmdEIRZKCPGdCQlRq
zF2BgWlXCzYZyBUzmeC9tP8Ie/6ekDQ0o90HNI+BAHOA21ZUXj9ZDhGFksiNb0Ie
4RtpJjWNKftTP/l5kZcdDdQ/HjXpNnKSSv2Bc+M8cpZk0OU2zT8Q92oy54Ot/jo6
MZFP2ZUnVEi6ryxNT4ZxEiQoCm6l+CFrF23R6AJSdGM4ttpcZfGMDl1JRiaBzolH
5fFOneMMqJ6rydyXKOvY2sKxpaN6xWS+TQpFMxRwxc3fu11pBiuPqM5HAbWUQxpT
y6fNt06t
=SAzV
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: segno
Source-Version: 1.5.2-3
Done: Timo Röhling 

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

Debian distribution maintenance software
pp.
Timo Röhling  (supplier of updated segno package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Jul 2023 20:20:00 +0200
Source: segno
Architecture: source
Version: 1.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Timo Röhling 
Closes: 1040571
Changes:
 segno (1.5.2-3) unstable; urgency=medium
 .
   * Team upload.
   * Depend on python3-pkg-resources for tests (Closes: #1040571)
Checksums-Sha1:
 275c6cada2471db268ac6baea7baafea530562cf 2040 segno_1.5.2-3.dsc
 616214e16ab7b9c97a8ffa307b5f93dc7dc23b78 4112 segno_1.5.2-3.debian.tar.xz
 ad3a759eb918f1b1e25f91a051fd5ff750b1c091 6628 segno_1.5.2-3_amd64.buildinfo
Checksums-Sha256:
 102832bfd0eeefe5254e305b1feeff196cae20974dab5d7f28845c55d95e952a 2040 
segno_1.5.2-3.dsc
 ac8c27e5c18d58cc2dc9361d9ba323185754f2b5a619302cbd3fffb1ac9a39b7

Processed: Bug#1040568 marked as pending in weresync

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040568 [src:weresync] weresync: implicitly depends on python3-py
Ignoring request to alter tags of bug #1040568 to the same tags previously set

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

Bug#1040568: marked as pending in weresync

[Timo Röhling]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/weresync/-/commit/81170e560400ff938a21110368da8df78cdf51a9


Use pytest, not py.test

Closes: #1040568


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040568

Processed: Bug#1040424 marked as pending in python-pytest-random-order

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040424 [src:python-pytest-random-order] python-pytest-random-order: 
implicitly depends on python3-py
Added tag(s) pending.

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

Bug#1040424: marked as pending in python-pytest-random-order

[Timo Röhling]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-pytest-random-order/-/commit/db3b39bd97ac3badfc5aa4c171e21256c209b0ad


Add missing depend on python3-py

Closes: #1040424


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040424

Processed: Bug#1040571 marked as pending in segno

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040571 [src:segno] segno: implicitly depends on python3-pkg-resources
Added tag(s) pending.

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

Bug#1040571: marked as pending in segno

[Timo Röhling]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/segno/-/commit/c5a8a9469abda2fd3698207b7e48f5a2d5092044


Depend on python3-pkg-resources for tests

Closes: #1040571


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040571

Processed: severity of 1041262 is important, severity of 1041264 is important

[Debian Bug Tracking System]

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

> severity 1041262 important
Bug #1041262 [src:casparcg-server] casparcg-server: dependens on removed 
fonts-liberation2
Severity set to 'important' from 'serious'
> severity 1041264 important
Bug #1041264 [src:fonts-recommended] fonts-recommended: depends on removed 
fonts-liberation2
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1041264: fonts-recommended: depends on removed fonts-liberation2

[Sebastian Ramacher]

Contro: severity -1 important

On 2023-07-16 18:47:44 +0200, Fabian Greffrath wrote:
> Why the severity? The fonts-liberation2 package is now a transitional package 
> which pulls in the actual fonts-liberation package. Von meinem/meiner Galaxy 
> gesendet

I missed that. britney was failing to remove src:fonts-liberation2
from testing for some time now but failed due to installability issues.
Lowering the severity.

Cheers
-- 
Sebastian Ramacher

Bug#1041260: wike: BD-Uninstallable: libadwaita-1-dev:amd64 (>= 1.3)

[Sebastian Ramacher]

On 2023-07-16 18:24:17 +0100, Simon McVittie wrote:
> On Sun, 16 Jul 2023 at 17:46:04 +0200, Sebastian Ramacher wrote:
> > Dependency installability problem for wike on amd64:
> > 
> > wike build-depends on missing:
> > - libadwaita-1-dev:amd64 (>= 1.3)
> 
> This will be fixed when the newer libadwaita-1-dev in experimental gets
> uploaded to unstable, presumably as part of GNOME 44. We've been delaying
> the upload of most of GNOME 44 to unstable until after the 12.1 point
> release, in order to get more testing for GNOME 43 packages' upstream
> bugfix releases as potential Debian 12 stable updates.
> 
> I think the only way to resolve this in unstable sooner would be to revert
> to wike 1.8.x with a +really version, which is probably not worth it when
> GNOME 44 is on the way anyway.

Yes, sure. But all this sounds like nobody actually tested the uploaded
wike version. The uploads should have gone to experimental …

Cheers
-- 
Sebastian Ramacher

Bug#1041260: wike: BD-Uninstallable: libadwaita-1-dev:amd64 (>= 1.3)

[Simon McVittie]

On Sun, 16 Jul 2023 at 17:46:04 +0200, Sebastian Ramacher wrote:
> Dependency installability problem for wike on amd64:
> 
> wike build-depends on missing:
> - libadwaita-1-dev:amd64 (>= 1.3)

This will be fixed when the newer libadwaita-1-dev in experimental gets
uploaded to unstable, presumably as part of GNOME 44. We've been delaying
the upload of most of GNOME 44 to unstable until after the 12.1 point
release, in order to get more testing for GNOME 43 packages' upstream
bugfix releases as potential Debian 12 stable updates.

I think the only way to resolve this in unstable sooner would be to revert
to wike 1.8.x with a +really version, which is probably not worth it when
GNOME 44 is on the way anyway.

smcv

Processed: severity of 1041059 is serious, severity of 1041225 is serious

[Debian Bug Tracking System]

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

> # suitesparse 7 transition has begun
> severity 1041059 serious
Bug #1041059 [src:libdogleg] FTBFS against suitesparse 7
Severity set to 'serious' from 'important'
> # suitesparse 7 transition has begun
> severity 1041225 serious
Bug #1041225 [src:siconos] FTBFS against suitesparse 7
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1037809: With relase 2023.04+ds-1 opm-material was merged into opm-common

[Markus Blatt]

Tags: wontfix

Dear all,

With the upstream release 2023.04 that I am currently uploading the code of
opm-material was merged into opm-common. Therefore there will be no fix for
this in opm-material as it should be removed anyway. Hopefully this will be
done by the autoremoval system without removing the rest of OPM.

Please note that in the recently uploaded version 2023.04+ds-1 of opm-common
(containing the failing code) this particular problem is fixed.

Cheers,

Markus Blatt

Bug#1037765: marked as done (maildir-utils: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 17:09:36 +
with message-id 
and subject line Bug#1037765: fixed in maildir-utils 1.8.14-2
has caused the Debian Bug report #1037765,
regarding maildir-utils: ftbfs with GCC-13
to be marked as done.

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

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


-- 
1037765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:maildir-utils
Version: 1.8.14-1
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/maildir-utils_1.8.14-1_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

[...]
   67 | throw Mu::Error{Error::Code::Command,
  |^~~~
mu-command-parser.cc:67:56: error: no matching function for call to 
‘Mu::Error::Error()’
../../lib/utils/mu-error.hh:93:9: note: candidate: ‘Mu::Error::Error(const 
Mu::Error&)’
   93 | Error(const Error& rhs) = default;
  | ^
../../lib/utils/mu-error.hh:93:9: note:   conversion of argument 1 would be 
ill-formed:
../../lib/utils/mu-error.hh:92:9: note: candidate: 
‘Mu::Error::Error(Mu::Error&&)’
   92 | Error(Error&& rhs)  = default;
  | ^
../../lib/utils/mu-error.hh:92:9: note:   conversion of argument 1 would be 
ill-formed:
mu-command-parser.cc:67:48: error: expected primary-expression before ‘{’ token
   67 | throw Mu::Error{Error::Code::Command,
  |^
mu-command-parser.cc:77:48: error: ‘Code’ is not a member of ‘Mu::Error’
   77 | throw Mu::Error{Error::Code::Command,
  |^~~~
mu-command-parser.cc:77:48: error: no matching function for call to 
‘Mu::Error::Error()’
../../lib/utils/mu-error.hh:93:9: note: candidate: ‘Mu::Error::Error(const 
Mu::Error&)’
   93 | Error(const Error& rhs) = default;
  | ^
../../lib/utils/mu-error.hh:93:9: note:   conversion of argument 1 would be 
ill-formed:
../../lib/utils/mu-error.hh:92:9: note: candidate: 
‘Mu::Error::Error(Mu::Error&&)’
   92 | Error(Error&& rhs)  = default;
  | ^
../../lib/utils/mu-error.hh:92:9: note:   conversion of argument 1 would be 
ill-formed:
mu-command-parser.cc:77:40: error: expected primary-expression before ‘{’ token
   77 | throw Mu::Error{Error::Code::Command,
  |^
mu-command-parser.cc:90:48: error: ‘Code’ is not a member of ‘Mu::Error’
   90 | throw Mu::Error{Error::Code::Command,
  |^~~~
mu-command-parser.cc:90:48: error: no matching function for call to 
‘Mu::Error::Error()’
../../lib/utils/mu-error.hh:93:9: note: candidate: ‘Mu::Error::Error(const 
Mu::Error&)’
   93 | Error(const Error& rhs) = default;
  | ^
../../lib/utils/mu-error.hh:93:9: note:   conversion of argument 1 would be 
ill-formed:
../../lib/utils/mu-error.hh:92:9: note: candidate: 
‘Mu::Error::Error(Mu::Error&&)’
   92 | Error(Error&& rhs)  = default;
  | ^
../../lib/utils/mu-error.hh:92:9: note:   conversion of argument 1 would be 
ill-formed:
mu-command-parser.cc:90:40: error: expected primary-expression before ‘{’ token
   90 | throw Mu::Error{Error::Code::Command,
  |

Bug#1041265: marked as done (gammaray: stop depending on qtwebengine5-dev on mipsel)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 17:04:49 +
with message-id 
and subject line Bug#1041265: fixed in gammaray 2.11.3-4
has caused the Debian Bug report #1041265,
regarding gammaray: stop depending on qtwebengine5-dev on mipsel
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.)


-- 
1041265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gammaray
Version: 2.11.3-3
Severity: serious
Tags: sid trixie

qtwebengine-opensource-src currently FTBFS on mipsel (see #1041250). To
complete the currently ongoing Qt transition, please disable support for
qtwebeninge-opensource-src on mipsel for the time being. This would
allow us to (temporarily) remove qtwebengine-opensource-src from mipsel.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: gammaray
Source-Version: 2.11.3-4
Done: Dmitry Shachnev 

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated gammaray package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Jul 2023 19:33:07 +0300
Source: gammaray
Built-For-Profiles: noudeb
Architecture: source
Version: 2.11.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Dmitry Shachnev 
Closes: 1041265
Changes:
 gammaray (2.11.3-4) unstable; urgency=medium
 .
   * Team upload.
   * Stop depending on qtwebengine5-dev on mipsel (closes: #1041265).
Checksums-Sha1:
 e400d520ef25364c045e3b3aadf568f536fe4b0d 3400 gammaray_2.11.3-4.dsc
 84e739b8ead74c4699c537bcbfbca059e509333f 20336 gammaray_2.11.3-4.debian.tar.xz
 cf84ab2a383c1c537df50771c443eebc95f2fe45 6013 
gammaray_2.11.3-4_source.buildinfo
Checksums-Sha256:
 985e3f33f45c37e4d39b4df157df9f9d3b709b7d33f3ac6dea67bcc2fb2e0a92 3400 
gammaray_2.11.3-4.dsc
 24fb63a76d4fe6498aa1427e81535058575394200ff564d7ed8a17dbd592120f 20336 
gammaray_2.11.3-4.debian.tar.xz
 2ed8619eef4cfda18ae97bc29676fea4b119e38227503ac573b09ea7eb7cda52 6013 
gammaray_2.11.3-4_source.buildinfo
Files:
 4d700c421468a2a5eba31e19ad54b0aa 3400 devel optional gammaray_2.11.3-4.dsc
 ebb3eaa06022f55d2648187cb7efab6a 20336 devel optional 
gammaray_2.11.3-4.debian.tar.xz
 397a653da68a61103868e27b18b115f2 6013 devel optional 
gammaray_2.11.3-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAmS0HHYTHG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDy5D+D/9KhisMLnF7vLJiTUJNdM2I9vuCKY/0
+zpgWei5wASRgv6dddYV07mfh2lFDqczBeQ/WPQ+ho97fCvIIgsR3VO/nFFZnfmu
T7DSSfLC1hJ7A9sMvXME6jqhKVUSzKAxjaRLHJgZAWG9ozCapiic3Q5+jFtrUjTd
Sr68/mR1K3ZKwI4VmfVBPHzjYePj0OaTG01FEFr9EpfQCGT2FJl155WGBiHO+jkp
lnZW/zSEO/KDRnvQ0vsT6ATqdR4XhuuM4hyy/YX23hcxWAtebgs+E0CswOmSQAcp
ynOeN363UwFdq98dfVlmoPZp2ka3gJmP6/SpBuO5CagkhLNJLW9E5SVAFFpkAXUM
hCJqKwtkKYUTxcEiXUqx1UFCyA0pEvORoC7whJqbID+YerIwGBc3Z1XOVw3WXPb9
Gmhq6sJBjynniz8KLKeMCZhoS7waF6YNWcQL6BgcbSwBGGe1ZATfONmQjAKLn3DR
UX75NGtbSWGscTSvBkEn0SRBZdNUntRO5Fd1DiijfneqGIjU1AkeNyS32gFE87eG
VhWX34CsHoLrZpMEAJegMQqF9+sbsCYV55uMIHZLw1fi6X30lq8IF1BwV8LHHCw1
wjk6jSsQEM5iVoqcjk97R7sRE05RnT4rO8+GxZ7xy6aHcS+TPx1MQV430CAX0o/V
pOqwgZ2vrjcM2w==
=0dwk
-END PGP SIGNATURE End Message ---

Bug#1041271: maildir-utils: public shared library shipped in maildir-utils binary package

[David Bremner]

Package: maildir-utils
Version: 1.8.14-2
Severity: serious
Justification: violates policy 8.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I think that libguile-mu.* need to be either moved to a private
directory or to their own packages. I don't know enough about guile to
say which is better.

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

Kernel: Linux 6.1.0-7-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

Versions of packages maildir-utils depends on:
ii  guile-3.0-libs  3.0.8-2
ii  libc6   2.37-3
ii  libgcc-s1   13.1.0-6
ii  libglib2.0-02.74.6-2
ii  libgmime-3.0-0  3.2.13+dfsg-2
ii  libreadline88.2-1.3
ii  libstdc++6  13.1.0-6
ii  libxapian30 1.4.22-1

maildir-utils recommends no packages.

maildir-utils suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmS0If4ACgkQA0U5G1Wq
FSFdlw//drvAFftKxrrn1Hk+A1wYL0ATPOgwI/61u3sC4P/uQRcTbC6zfJcO/uca
GJVFWaUHIFsmPr3lwQf6KkZweBtdnm38MXsXbxw7uBH5abEKoLPZCEr0FzArfZe/
CaPFMHgCl6/k25BNigIXUcx5rgvoLCjRYrh8RVvrIN/NWfEioYDYqYs4+ZEmswP3
fMOdoqfohtXlisfKrrI/ysK00gJpI0vWYJzdEcapirDy7eMtSBXOqjUz2a3kGJ/h
Oxtg1J1GCSp/pAb3lJvAojxITQI69ZAkX2T6xGqXUhGbRCKjVUulovI0iSQGbwM4
mKDMs5oH6kn8gM9z/HTUpoxhLE85KbMQjtsTx6MoXXZKPat02ipzloc3NqWQyBDj
pL8BEpnU6Hc0MtZLI6Q+gUG1akq5BmB24pKxrcEfAVRSdFXbOjfGIHjyH6achfcn
QwOz6R5kNte4VLfCOvWXhnsDvCeiOfePC/gaVqvvzJR5/iWMovDOdBTshK9uXWkl
3hgwYqRIYRtnKobz8QcOnqTbVxFiJv8gyaOm7cbhzKGfWeMFwv38mhmJXaRj7Znv
zb8MqG2eK89v8ZkD7RxsfVVOGOU94102QwlmQ6QOuB4etVyfuUkjjnRsjJgwSRE1
TtlYcHfIj8M2EgMPWEB2mjcFb/TKlx48+Br53YNk3z6mErYJtZk=
=HGuU
-END PGP SIGNATURE-

Bug#1037808: marked as done (opm-grid: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 18:31:58 +0200
with message-id 
and subject line Re: Bug#1037808: opm-grid: ftbfs with GCC-13
has caused the Debian Bug report #1037808,
regarding opm-grid: ftbfs with GCC-13
to be marked as done.

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

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


-- 
1037808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:opm-grid
Version: 2022.10+ds-3
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/opm-grid_2022.10+ds-3_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

[...]
  253 | constexpr GeometryType(unsigned int topologyId, unsigned int dim, 
bool isNone)
  |   ^~~~
/usr/include/dune/geometry/type.hh:524:71:   in ‘constexpr’ expansion of 
‘Dune::GeometryTypes::cube(2)’
/usr/include/dune/geometry/type.hh:524:73: error: ‘constexpr 
Dune::GeometryType::GeometryType(unsigned int, unsigned int, bool)’ called in a 
constant expression
  524 |   DUNE_INLINE_VARIABLE constexpr GeometryType quadrilateral = 
cube(2);
  | 
^
/usr/include/dune/geometry/type.hh:253:15: note: ‘constexpr 
Dune::GeometryType::GeometryType(unsigned int, unsigned int, bool)’ declared 
here
  253 | constexpr GeometryType(unsigned int topologyId, unsigned int dim, 
bool isNone)
  |   ^~~~
/usr/include/dune/geometry/type.hh:530:72:   in ‘constexpr’ expansion of 
‘Dune::GeometryTypes::simplex(3)’
/usr/include/dune/geometry/type.hh:530:74: error: ‘constexpr 
Dune::GeometryType::GeometryType(unsigned int, unsigned int, bool)’ called in a 
constant expression
  530 |   DUNE_INLINE_VARIABLE constexpr GeometryType tetrahedron = 
simplex(3);
  | 
 ^
/usr/include/dune/geometry/type.hh:253:15: note: ‘constexpr 
Dune::GeometryType::GeometryType(unsigned int, unsigned int, bool)’ declared 
here
  253 | constexpr GeometryType(unsigned int topologyId, unsigned int dim, 
bool isNone)
  |   ^~~~
/usr/include/dune/geometry/type.hh:536:88: error: ‘constexpr 
Dune::GeometryType::GeometryType(unsigned int, unsigned int, bool)’ called in a 
constant expression
  536 |   DUNE_INLINE_VARIABLE constexpr GeometryType pyramid = 
GeometryType(0b0011,3,false);
  | 
   ^
/usr/include/dune/geometry/type.hh:253:15: note: ‘constexpr 
Dune::GeometryType::GeometryType(unsigned int, unsigned int, bool)’ declared 
here
  253 | constexpr GeometryType(unsigned int topologyId, unsigned int dim, 
bool isNone)
  |   ^~~~
/usr/include/dune/geometry/type.hh:542:86: error: ‘constexpr 
Dune::GeometryType::GeometryType(unsigned int, unsigned int, bool)’ called in a 
constant expression
  542 |   DUNE_INLINE_VARIABLE constexpr GeometryType prism = 
GeometryType(0b0101,3,false);
  | 
 ^
/usr/include/dune/geometry/type.hh:253:15: note: ‘constexpr 
Dune::GeometryType::GeometryType(unsigned int, unsigned int, bool)’ declared 
here
  253 | constexpr GeometryType(unsigned int topologyId, unsigned int dim, 
bool isNone)
  |   ^~~~
/usr/include/dune/geometry/type.hh:548:68:   in ‘constexpr’ expansion of 
‘Dune::GeometryTypes::cube(

Bug#1037788: marked as done (nextpnr: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 18:04:50 +0200
with message-id <6cb4090e-f829-42fb-9aa7-34dbfd0c5...@darkboxed.org>
and subject line Re: nextpnr: ftbfs with GCC-13
has caused the Debian Bug report #1037788,
regarding nextpnr: ftbfs with GCC-13
to be marked as done.

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

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


-- 
1037788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nextpnr
Version: 0.4-1
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/nextpnr_0.4-1_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

[...]
In file included from /<>/common/kernel/log.h:30,
 from /<>/common/kernel/bits.cc:26:
/<>/common/kernel/hashlib.h:79:29: error: ‘uint32_t’ was not 
declared in this scope
   79 | template <> struct hash_ops : hash_int_ops
  | ^~~~
/<>/common/kernel/hashlib.h:22:1: note: ‘uint32_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
   21 | #include "nextpnr_assertions.h"
  +++ |+#include 
   22 | #include "nextpnr_namespaces.h"
/<>/common/kernel/hashlib.h:79:37: error: template argument 1 is 
invalid
   79 | template <> struct hash_ops : hash_int_ops
  | ^
/<>/common/kernel/hashlib.h:83:29: error: ‘uint64_t’ was not 
declared in this scope
   83 | template <> struct hash_ops : hash_int_ops
  | ^~~~
/<>/common/kernel/hashlib.h:83:29: note: ‘uint64_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
/<>/common/kernel/hashlib.h:83:37: error: template argument 1 is 
invalid
   83 | template <> struct hash_ops : hash_int_ops
  | ^
/<>/common/kernel/hashlib.h: In static member function ‘static 
unsigned int nextpnr_generic::hash_ptr_ops::hash(const void*)’:
/<>/common/kernel/hashlib.h:170:62: error: ‘uintptr_t’ was not 
declared in this scope
  170 | static inline unsigned int hash(const void *a) { return 
(uintptr_t)a; }
  |  ^
/<>/common/kernel/hashlib.h:170:62: note: ‘uintptr_t’ is defined 
in header ‘’; did you forget to ‘#include ’?
/<>/common/kernel/hashlib.h:170:72: error: expected ‘;’ before ‘a’
  170 | static inline unsigned int hash(const void *a) { return 
(uintptr_t)a; }
  |^
make[4]: *** [CMakeFiles/nextpnr-generic-test.dir/build.make:107: 
CMakeFiles/nextpnr-generic-test.dir/common/kernel/bits.cc.o] Error 1
make[4]: *** Waiting for unfinished jobs
In file included from /<>/common/kernel/log.h:30,
 from /<>/common/kernel/archcheck.cc:20:
/<>/common/kernel/hashlib.h:79:29: error: ‘uint32_t’ was not 
declared in this scope
   79 | template <> struct hash_ops : hash_int_ops
  | ^~~~
/<>/common/kernel/hashlib.h:22:1: note: ‘uint32_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
   21 | #include "nextpnr_assertions.h"
  +++ |+#include 
   22 | #include "nextpnr_namespaces.h"
/<>/common/kernel/hashlib.h:79:37: error: template argument 1 is 
invalid
   79 | template <> struct hash_ops : hash_int_ops
  | ^
/<>/common/kernel/hashlib.h:83:29: error: ‘uint64_t’ was not 
declared in this scope
   83 | template <> struct hash_ops : hash_int_ops
  | ^~~~
/<>/common/

Bug#1041264: fonts-recommended: depends on removed fonts-liberation2

[Fabian Greffrath]

Why the severity? The fonts-liberation2 package is now a transitional package 
which pulls in the actual fonts-liberation package. Von meinem/meiner Galaxy 
gesendet

Bug#1037810: opm-upscaling: ftbfs with GCC-13

[Markus Blatt]

Package: src:opm-upscaling
Version: 2022.10+ds-4

It turned out the bug was not in opm-grid but in dune-geometry which caused
the build here to fail (see bug #1037631). With the upload of version 2.9.0-3 
of dune-geometry we believe that the bug you reported is fixed.


Cheers,

Markus Blatt

Bug#1041264: fonts-recommended: depends on removed fonts-liberation2

[Fabian Greffrath]

Why the severity? The fonts-liberation2 package is now a transitional package 
which pulls in the actual fonts-liberation package. Von meinem/meiner Galaxy 
gesendet

Bug#1041270: dynarmic: broke ABI without SONAME bump

[Sebastian Ramacher]

Source: dynarmic
Version: 6.4.8+ds-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/y/yuzu/35884387/log.gz

 60s yuzu-cmd: symbol lookup error: yuzu-cmd: undefined symbol: 
_ZN8Dynarmic3A327Context4RegsEv

Cheers
-- 
Sebastian Ramacher

Processed: RM: qtwebengine-opensource-src [mipsel] -- RoQA; FTBFS on mipsel

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:qtwebengine-opensource-src
Bug #1041268 [ftp.debian.org] RM: qtwebengine-opensource-src [mipsel] -- RoQA; 
FTBFS on mipsel
Added indication that 1041268 affects src:qtwebengine-opensource-src
> block -1 by 1041266 1041265 1041267
Bug #1041268 [ftp.debian.org] RM: qtwebengine-opensource-src [mipsel] -- RoQA; 
FTBFS on mipsel
1041268 was not blocked by any bugs.
1041268 was not blocking any bugs.
Added blocking bug(s) of 1041268: 1041267, 1041266, and 1041265

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

Bug#1041260: wike ftbfs

[Matthias Geiger]

Hi Sebastian,

this happened due to an untimely upload of mine. The required libadwaita 
(1.3) is already in experimental; according to the GNOME team they won't 
upload it until after the bookworm 12.1


update. For now all we can do is wait.

cheers

--
Matthias Geiger (werdahias)


OpenPGP_0x18BD106B3B6C5475.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1041253: marked as done (pyside2: stop depending on qtwebengine5-dev on mipsel)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 16:14:28 +
with message-id 
and subject line Bug#1041253: fixed in pyside2 5.15.10-3
has caused the Debian Bug report #1041253,
regarding pyside2: stop depending on qtwebengine5-dev on mipsel
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.)


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

qtwebengine-opensource-src currently FTBFS on mipsel (see #1041250). To
complete the currently ongoing Qt transition, please disable support for
qtwebeninge-opensource-src on mipsel for the time being. This would
allow us to (temporarily) remove qtwebengine-opensource-src from mipsel.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: pyside2
Source-Version: 5.15.10-3
Done: Dmitry Shachnev 

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated pyside2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Jul 2023 17:49:14 +0300
Source: pyside2
Architecture: source
Version: 5.15.10-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Dmitry Shachnev 
Closes: 1041253
Changes:
 pyside2 (5.15.10-3) unstable; urgency=medium
 .
   * Team upload.
   * Stop building the Qt WebEngine package on mipsel (closes: #1041253).
Checksums-Sha1:
 df9f271f8f2d8a39714fba77a33f5d3947382a90 7736 pyside2_5.15.10-3.dsc
 5ba7f0298b72f550bfd21de2f8edb17199615965 19920 pyside2_5.15.10-3.debian.tar.xz
 50d3d1015585d070f5447b8c76850e1988fdb0e9 14479 
pyside2_5.15.10-3_source.buildinfo
Checksums-Sha256:
 a710e4bf1265dc091d70b119d16a1a7be427f5d8c8c09a12673127b4f383b47f 7736 
pyside2_5.15.10-3.dsc
 4131ba9b03d1f1fa947fc57ed9157e99971297f64c6c471d58c6ca6285acf917 19920 
pyside2_5.15.10-3.debian.tar.xz
 224bd76477f25190ba3a507347a71a527c69a99ef5fe37d9253dfbf817ab 14479 
pyside2_5.15.10-3_source.buildinfo
Files:
 fbe2315594e1a464d9c1387b26705147 7736 python optional pyside2_5.15.10-3.dsc
 7cb23398dfc003a62e4354985261b426 19920 python optional 
pyside2_5.15.10-3.debian.tar.xz
 33b3eee00b07cbae7b32c1d56833fadb 14479 python optional 
pyside2_5.15.10-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAmS0A8MTHG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDy6QJD/42caKk44WO3jR6qbdvN0+WeemcwDTK
GLqDQ+iMeJbKz1c18TIK4r6lL/6cfImdsikTFrEmR9/fwUlqbxRosV1kage4UH3B
6zHT35ykShgZ8bSX0xDpiS0MFhKg3+NeALyOYdABiqPelCaZq6FsVREN76oPx3rk
MNrsOde7xArgL00LLk3u9tKsB7vlqccKIaVxllfM+xo9ggHEGXSSiqa4vGix4sPP
QEqzLDpposg/z9XF7FlNAVLLhX3bFUv4NOYOrLVGNT/vsvg2St1dEFC3/FoDxq73
yfgp3SXvB//TYK/LtXK2YxKoZPVnDKUfvZxG0WlsPP+I0/VBIxppQ2OOa+qwj/Cx
0nCYy0dXmF1IDFLsnOOi8Cbmvo2o3fvnCyL88/hZA/FO+iLy8Dvg54nqOAlEx4XS
t6FsmslUAPTv5QAc/2hEgUAylJdQ6rCGarxfpfZLwCCiU2vmtfMkicFLex0AyYMC
Ln0wUDeIzPpiZyQBoJo9IbzEUISFQqt8bFH8RUlgVNa5yQkf6OSQ9gCH4P9h3Cp8
5e9c3b4su8hvRYtwvGEixiwTS6zFtqZo6vKHOU4KV27tbK8oBiSX3GC4RTdUFtCu
AMCbO/xsiJ2H6NGYwavdmY5+ZTUsFO0nmeZ62+8FotQirOaIXZ0whpAP5T4zupaD
Rj1pFMPimOxTTA==
=zPXJ
-END PGP SIGNATURE End Message ---

Bug#1041265: gammaray: stop depending on qtwebengine5-dev on mipsel

[Sebastian Ramacher]

Source: gammaray
Version: 2.11.3-3
Severity: serious
Tags: sid trixie

qtwebengine-opensource-src currently FTBFS on mipsel (see #1041250). To
complete the currently ongoing Qt transition, please disable support for
qtwebeninge-opensource-src on mipsel for the time being. This would
allow us to (temporarily) remove qtwebengine-opensource-src from mipsel.

Cheers
-- 
Sebastian Ramacher

Bug#1041252: marked as done (libksysguard: stop depending on qtwebengine5-dev on mipsel)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 16:10:07 +
with message-id 
and subject line Bug#1041252: fixed in libksysguard 4:5.27.5-3
has caused the Debian Bug report #1041252,
regarding libksysguard: stop depending on qtwebengine5-dev on mipsel
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.)


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

qtwebengine-opensource-src currently FTBFS on mipsel (see #1041250). To
complete the currently ongoing Qt transition, please disable support for
qtwebeninge-opensource-src on mipsel for the time being. This would
allow us to (temporarily) remove qtwebengine-opensource-src from mipsel.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: libksysguard
Source-Version: 4:5.27.5-3
Done: Patrick Franz 

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

Debian distribution maintenance software
pp.
Patrick Franz  (supplier of updated libksysguard package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Jul 2023 16:56:16 +0200
Source: libksysguard
Architecture: source
Version: 4:5.27.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Patrick Franz 
Closes: 1041252
Changes:
 libksysguard (4:5.27.5-3) unstable; urgency=medium
 .
   [ Patrick Franz ]
   * Do not depend on qtwebengine5-dev on mipsel (Closes: #1041252).
Checksums-Sha1:
 1583752e5121d3e2b6709dbc29d0df7d5046814d 4115 libksysguard_5.27.5-3.dsc
 7baa6e21c2b70579a0dc17806b24813687fc06a8 30448 
libksysguard_5.27.5-3.debian.tar.xz
 291a2eb1022fe30808bd9501a8dbd97320881608 15392 
libksysguard_5.27.5-3_source.buildinfo
Checksums-Sha256:
 0b7c3ef23e283156daa37717e487b85abc9be5d3d58075b470218c00dade9331 4115 
libksysguard_5.27.5-3.dsc
 c74b5ec3ca05258986eea7090868a52ef0240f731b3c293d27740a51c7a5bec6 30448 
libksysguard_5.27.5-3.debian.tar.xz
 6ee3f0aa95b988f2971d36f2f8a6bbcf2052599687039b82d1235b87fa0edd23 15392 
libksysguard_5.27.5-3_source.buildinfo
Files:
 b5cc5188d4647afa0b87a7d83984a72f 4115 libs optional libksysguard_5.27.5-3.dsc
 8a13682f458e749c2a88e91dd282c9c4 30448 libs optional 
libksysguard_5.27.5-3.debian.tar.xz
 9a05d25588405397a7541fcc794ed04f 15392 libs optional 
libksysguard_5.27.5-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEYodBXDR68cxZHu3Knp96YDB3/lYFAmS0BlAACgkQnp96YDB3
/laDoQ/+PbsFPrnR/jbznA/YkAzmic/s/vrsdqrmEhcuakr9T7RHbOGxQEZiqgVc
Aw39PP0HTJtvRuLBXRoXxygireuYWFMaiFL18krH2td1KkisLg5XzePjvuKf4MNc
m41Wy7N209qfFfAnjWVSMFr1io4sRn6gA6f07kIz0HMDt3YhI+MGPcntL+iZJKt5
iWX9pASYOMzxQbjHji0gzh35y1wt2O4PhvcM5xUCwDIZ3PfJsOepIx/KTInq/oCu
dkqQq7ZbMYJnzoPkXa77t2PXDF+aA+MTEkKxkwVHAYMR7c6slHZNvXxlUxYsB57s
UVqL6MTjgZ9khgctJHQV7ctQc6Upxne05IKvFIy+kZ0Q1fUxpFP3g6f1yAEQlcQO
ckGgti4St/hfqrtvPBEEun/PuP+FsbyuMZbsK56Ctu1eE/cLPUZrPzFpmPgGbeYX
dQLEMH3AB00jQUT5K6LXaMoz5QNukGVMlL0g6u7Ws/poTPW9KNDjihCDmz/wbjO8
gEfQ3VRk/G1DYB8enb5F6M5riDr4uGOKWwq92kvi8J1WOI4q76nPfXjL0Sgo5b0o
Sf+VdVd39ZlKyV+4ykzG5V6JJhJUceE5kruqk0RhDftr5Ium0W7UeovUuLKJ9q56
XXarnHA9PFy9VFi5sqyPMFKOg+lQu0mv6+/zGqkXDP8c79WJ0/w=
=k4Tr
-END PGP SIGNATURE End Message ---

Bug#1041264: fonts-recommended: depends on removed fonts-liberation2

[Sebastian Ramacher]

Source: fonts-recommended
Version: 1
Severity: serious
Tags: sid trixie

One or more binary packages produced by fonts-recommended depends on
fonts-liberation2. The font is now provided by fonts-liberation. See
#1038940. Please update the dependency.

Cheers
-- 
Sebastian Ramacher

Bug#1041263: fontconfig: depends on removed fonts-liberation2

[Sebastian Ramacher]

Source: fontconfig
Version: 2.14.1-4
Severity: serious
Tags: sid trixie

One or more binary packages produced by fontconfig depends on
fonts-liberation2. The font is now provided by fonts-liberation. See
#1038940. Please update the dependency.

Cheers
-- 
Sebastian Ramacher

Bug#1041262: casparcg-server: dependens on removed fonts-liberation2

[Sebastian Ramacher]

Source: casparcg-server
Version: 2.3.3+dfsg-3
Severity: serious
Tags: sid trixie

One or more binary packages produced by casparcg-server depends on
fonts-liberation2. The font is now provided by fonts-liberation. See
#1038940. Please update the dependency.

Cheers
-- 
Sebastian Ramacher

Bug#1041260: wike: BD-Uninstallable: libadwaita-1-dev:amd64 (>= 1.3)

[Sebastian Ramacher]

Source: wike
Version: 2.0.1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/package.php?p=wike&suite=sid

Dependency installability problem for wike on amd64:

wike build-depends on missing:
- libadwaita-1-dev:amd64 (>= 1.3)


Cheers
-- 
Sebastian Ramacher

Bug#1041259: freedv: FTBFS: lpcnet_freedv.h: No such file or directory

[Sebastian Ramacher]

Source: freedv
Version: 1.8.11-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=freedv&arch=amd64&ver=1.8.11-1%2Bb2&stamp=1689518012&raw=0

[ 95%] Building CXX object src/CMakeFiles/freedv.dir/ongui.cpp.o
cd /<>/Build/src && /usr/bin/c++ -DAUDIO_ENGINE_PULSEAUDIO_ENABLE 
-DGIT_HASH=\"None\" -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ 
-I/<>/src -I/<>/Build/src -I/<>/Build 
-isystem /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem 
/usr/include/wx-3.2 -isystem /usr/include/codec2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pthread -O2 -g 
-DNDEBUG -std=c++14 -MD -MT src/CMakeFiles/freedv.dir/ongui.cpp.o -MF 
CMakeFiles/freedv.dir/ongui.cpp.o.d -o CMakeFiles/freedv.dir/ongui.cpp.o -c 
/<>/src/ongui.cpp
/<>/src/ongui.cpp:8:10: fatal error: lpcnet_freedv.h: No such file 
or directory
8 | #include "lpcnet_freedv.h"
  |  ^
compilation terminated.
make[3]: *** [src/CMakeFiles/freedv.dir/build.make:345: 
src/CMakeFiles/freedv.dir/ongui.cpp.o] Error 1
Cheers
-- 
Sebastian Ramacher

Bug#1041258: rust-fs-extra: FTBFS: test failures

[Sebastian Ramacher]

Source: rust-fs-extra
Version: 1.3.0-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=rust-fs-extra&arch=amd64&ver=1.3.0-1&stamp=1688994742&raw=0


failures:
it_copy_progress_work

it_copy_with_progress_inside_no_overwrite_work_target_dir_exist_with_source_dir_exist

it_copy_with_progress_inside_overwrite_work_target_dir_exist_with_source_dir_exist

it_copy_with_progress_inside_work_target_dir_exist_with_no_source_dir_named_sub_dir
it_copy_with_progress_inside_work_target_dir_not_exist
it_copy_with_progress_work_dif_buf_size
it_get_dir_content
it_get_dir_content_many_levels

it_move_dir_with_progress_inside_no_overwrite_work_target_dir_exist_with_source_dir_exist

it_move_dir_with_progress_inside_overwrite_work_target_dir_exist_with_source_dir_exist

it_move_dir_with_progress_inside_work_target_dir_exist_with_no_source_dir_named_sub_dir
it_move_dir_with_progress_inside_work_target_dir_not_exist
it_move_progress_work
it_move_with_progress_work_dif_buf_size

test result: FAILED. 68 passed; 14 failed; 0 ignored; 0 measured; 0 filtered 
out; finished in 0.05s

error: test failed, to rerun pass `--test dir`
dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 
101
make[1]: *** [debian/rules:7: override_dh_auto_test] Error 25


Cheers
-- 
Sebastian Ramacher

Bug#1041257: flatbuffers: FTBFS on amd64: symbol differences

[Sebastian Ramacher]

Source: flatbuffers
Version: 2.0.8+dfsg1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=flatbuffers&arch=amd64&ver=2.0.8%2Bdfsg1-3&stamp=1689315457&raw=0

+++ dpkg-gensymbols01uTG6   2023-07-14 06:17:31.308919257 +
@@ -286,6 +286,8 @@
  (optional=templinst)_ZNK11flexbuffers9Reference8AsDoubleEv@Base 
1.12.0~git20200706.969d0f7
  (optional=templinst)_ZNK11flexbuffers9Reference8AsUInt64Ev@Base 
1.12.0~git20200706.969d0f7
  _ZNKSt5ctypeIcE8do_widenEc@Base 1.12.0~git20200706.969d0f7
+ _ZNSt12_Vector_baseIjSaIjEED1Ev@Base 2.0.8+dfsg1-3
+ _ZNSt12_Vector_baseIjSaIjEED2Ev@Base 2.0.8+dfsg1-3
  _ZNSt14_Function_baseD1Ev@Base 2.0.8
  _ZNSt14_Function_baseD2Ev@Base 2.0.8
  
_ZNSt17_Function_handlerIFccEPS0_E10_M_managerERSt9_Any_dataRKS3_St18_Manager_operation@Base
 2.0.8
@@ -293,8 +295,8 @@
  
(optional=templinst)_ZNSt3setISt4pairIN11flatbuffers8BaseTypeEPNS1_9StructDefEESt4lessIS5_ESaIS5_EE6insertEOS5_@Base
 1.12.0~git20200706.969d0f7
  
(optional=templinst)_ZNSt6vectorIN11flexbuffers7Builder5ValueESaIS2_EE17_M_default_appendEm@Base
 1.12.1~git20200711.33e2d80
  (optional=templinst)_ZNSt6vectorIhSaIhEE17_M_default_appendEm@Base 
1.12.1~git20200711.33e2d80
- _ZNSt6vectorIjSaIjEED1Ev@Base 2.0.8
- _ZNSt6vectorIjSaIjEED2Ev@Base 2.0.8
+#MISSING: 2.0.8+dfsg1-3# _ZNSt6vectorIjSaIjEED1Ev@Base 2.0.8
+#MISSING: 2.0.8+dfsg1-3# _ZNSt6vectorIjSaIjEED2Ev@Base 2.0.8
  
_ZNSt8_Rb_treeIN11flatbuffers12IncludedFileES1_St9_IdentityIS1_ESt4lessIS1_ESaIS1_EE24_M_get_insert_unique_posERKS1_@Base
 2.0.8
  
(optional=templinst)_ZNSt8_Rb_treeIN11flatbuffers6OffsetINS0_6StringEEES3_St9_IdentityIS3_ENS0_17FlatBufferBuilder19StringOffsetCompareESaIS3_EE16_M_insert_uniqueIRKS3_EESt4pairISt17_Rb_tree_iteratorIS3_EbEOT_@Base
 1.12.0~git20200706.969d0f7
  
(optional=templinst)_ZNSt8_Rb_treeISt4pairImmES1_St9_IdentityIS1_EN11flexbuffers7Builder19StringOffsetCompareESaIS1_EE16_M_insert_uniqueIRKS1_EES0_ISt17_Rb_tree_iteratorIS1_EbEOT_@Base
 1.12.1~git20200711.33e2d80
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:11: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher

Bug#1041207: debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE

[Ansgar]

On Sun, 2023-07-16 at 12:54 +0100, Simon McVittie wrote:
> On Sun, 16 Jul 2023 at 12:42:11 +0100, Luca Boccassi wrote:
> > In the meanwhile, I'll immediately revert the sabotage.
> 
> Both of you, please don't turn this into an NMU war in the archive:
> that doesn't benefit anyone. I would have preferred it if Adam had not
> immediately uploaded a 0-day revert, but preserving the status quo from
> bookworm is not the worst state to be in while we discuss this.

No, we should just have made a decision a long time ago and not go back
and forth the entire time. That we do not do that shows lack of
leadership in Debian.

(And yes, you can reconsider stuff, but the barrier to stop a process
and reconsider it again should not be zero and probably higher the
later one does block progress.)

> If Adam's concerns about this change are valid, then we should address
> them, either by doing something different in debootstrap or by reporting
> bugs against affected packages.

I guess Adam could go ahead with the GR he wanted to bring up the last
time he did NMUs this way (for reverting enabling usrmerge by default
on upgrades).  I would like to ask Adam to stop interfering with
usrmerge until that long announced GR is there (and note that if we
waited for that GR to happen as Adam demanded then we would still be
waiting).

> If Adam's concerns about this change turn out to be unfounded, then we
> should reinstate my change (as NMU'd by Luca) in a calm and considered
> way, and all we will have lost is a few days of progress and a few bytes
> of changelog.

That is false in so far as that only considers technical changes we
get. However we also lose more and more energy/motivation/* even if we
eventually go ahead as planned, i.e., social costs are not considered,
but should be (IMHO).

Ansgar

Bug#1040631: marked as done (imgp autopkg tests fail with pillow 10.0.0)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 15:13:33 +
with message-id 
and subject line Bug#1040631: fixed in imgp 2.8+git20230219.3d60e58-1
has caused the Debian Bug report #1040631,
regarding imgp autopkg tests fail with pillow 10.0.0
to be marked as done.

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

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


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

Package: src:imgp
Version: 2.8-2
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/i/imgp/35498775/log.gz

 27s autopkgtest [17:23:03]: test test: [---
 27s Traceback (most recent call last):
 27s   File "/usr/bin/imgp", line 54, in 
 27s png_ip = PIL.Image.ANTIALIAS  # default interpolation for PNG
 27s  ^^^
 27s AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'
 28s autopkgtest [17:23:04]: test test: ---]
--- End Message ---
--- Begin Message ---
Source: imgp
Source-Version: 2.8+git20230219.3d60e58-1
Done: SZ Lin (林上智) 

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

Debian distribution maintenance software
pp.
SZ Lin (林上智)  (supplier of updated imgp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Jul 2023 18:10:42 +0800
Source: imgp
Architecture: source
Version: 2.8+git20230219.3d60e58-1
Distribution: unstable
Urgency: medium
Maintainer: SZ Lin (林上智) 
Changed-By: SZ Lin (林上智) 
Closes: 1040631
Changes:
 imgp (2.8+git20230219.3d60e58-1) unstable; urgency=medium
 .
   * Fix imgp autopkg tests fail with pillow 10.0.0 (Closes: #1040631)
   * d/control:
 - Bump Standards-Version to 4.6.1.0
   * d/copyright:
 - Update copyright year
   * d/patch:
 - Tweak the context
Checksums-Sha1:
 898547c4ad3023b5ac617f1397833a43bf36518e 1971 
imgp_2.8+git20230219.3d60e58-1.dsc
 ffa18359ca438718aec128d768c7588782d634ce 28482 
imgp_2.8+git20230219.3d60e58.orig.tar.gz
 15faef8afd61acc2359ed8e8d3919abd4e0527f6 3540 
imgp_2.8+git20230219.3d60e58-1.debian.tar.xz
 d10ace5b1682ee642f170f453a0cf7daaec8319d 6922 
imgp_2.8+git20230219.3d60e58-1_amd64.buildinfo
Checksums-Sha256:
 e924046887f6317e9dccefae96c6a0ce0b15761adf17438954c0d706718089b7 1971 
imgp_2.8+git20230219.3d60e58-1.dsc
 8a1bd1882dcfe110b2fc3b92e006c7c6db89f209518321511b7ab9c05585d71e 28482 
imgp_2.8+git20230219.3d60e58.orig.tar.gz
 835b4fb1858c3ba2af0faf1b75386ab2a3a5605e66b177231c1ba16af462e3d4 3540 
imgp_2.8+git20230219.3d60e58-1.debian.tar.xz
 81da99a2a40d51701339d1799afe028ed58c214ea96f1f934547df5606a7916e 6922 
imgp_2.8+git20230219.3d60e58-1_amd64.buildinfo
Files:
 37479cddeb0b6139b95b2713f4e91ac8 1971 misc optional 
imgp_2.8+git20230219.3d60e58-1.dsc
 df916feacf8595c36ea3e36c9cae19c2 28482 misc optional 
imgp_2.8+git20230219.3d60e58.orig.tar.gz
 7d06d151f8c8afb87568c3c2a5e85ca3 3540 misc optional 
imgp_2.8+git20230219.3d60e58-1.debian.tar.xz
 22bbb45063dff8821e9c0544a2f612eb 6922 misc optional 
imgp_2.8+git20230219.3d60e58-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEF4+DOLMUAeME/ES6qVmzipVh8/kFAmSz81YACgkQqVmzipVh
8/krCQ//e1gOf7DBXi/4EqTRUU2rRDrGn7QWZsVjjTOznyAe3L5xCUVMNn2ECMGq
4Mkj3FYH/7JS1ocGNN3k0kYXwkEUYobDqoKjTSuGCc0qqmZs11E0IUdszCSQ1qSm
tigN5eV2o+KGy4rN8/ny04InHh7ddOg6fMnP+lbVm7yX0fBzy52hiwwvR1LiVlPc
ie2xZhf0JhgbiMqDk9cTvgKDNxlmYKNqBV6GSABU9RwDrtLfwtF70LPcSL4hb7CG
yRQW3Ix12/aCQpBgl9AGUPtgLPLfeIwQ6Nr7H7zteaNVbRCqb4LWFdV+HQx1zApw
xJo1/WXBmWFacFeXDAz3u2VsrqC9oWsy1zzrcSBY5Q91fUI2RyJ3N9T7dJm2cIIO
RpOCrDR74/MXwuQS1gaAZfejhH3jcSc3pmqzNlCmtbD66i+t/KWU7AXD4pk0zePY
GNWriwWQh3rK5a17FBWILny1+ybVb+6ZNSXX2KfVTJfuaVtZg/MQ3/MIJK/ZAQ6u
SnoUAuIlDrIIU2VFRmSK9Lsn5qFNNTdM5ZL+xKAiBnTwwjbRatNRU4p2wdDXL21W
g+UMb7k1Gsm8RMWnsy+50RcId8pRD+ewc064K1vmmlkcMIARlUffgd7qA5MXTdIA
ujvob9XCAr8HPR0nNvZOvGffSgt7d/Hy/aA5yOsCcHuaBNXRQIo=
=RwYS
-END PGP SIGNATURE End Message ---

Bug#1034348: at: autopkgtest regression on arm64

[Jose M Calhariz]

Hi, I believe my last update fixed the problem can someone double check?

Kind regards
Jose M Calhariz


On July 7, 2023 11:26:22 AM GMT+01:00, Jose M Calhariz  
wrote:
>I too think it's a race condition. I made some changes to the test but the 
>upload to Debian did not went well.
>
>
>On July 6, 2023 2:12:59 PM GMT+01:00, Vincent Lefevre  
>wrote:
>>On 2023-07-05 18:58:13 +0200, Johannes Christ wrote:
>>> Is there another way to reproduce this issue?
>>
>>I'm wondering whether there is a race condition in the test:
>>
>># use at command to schedule a job.
>>echo "echo `date` > ${WORKDIR}/${TMPFILE}" | at now + 1 minute
>>
>>So the file is expected to be created 1 minute later.
>>
>>Then in the script:
>>
>>sleep 2
>>
>>[...]
>>
>>sleep 58
>>
>>if grep -Fq "UTC" $WORKDIR/$TMPFILE
>>
>>[...]
>>
>>So the script waits for 1 minute (and some other fast commands)
>>before checking the existence of the file, which is the wait time
>>given to "at".
>>
>>I can see 2 possible issues:
>>
>>1. The system is a bit slow, and the job execution will take a bit
>>more time.
>>
>>2. Time inaccuracies. What are the guaranties given by the system?
>>
>>-- 
>>Vincent Lefèvre  - Web: 
>>100% accessible validated (X)HTML - Blog: 
>>Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: Bug#1041254: docker.io: FTBFS: test failures

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/moby/moby/pull/45972
Bug #1041254 [src:docker.io] docker.io: FTBFS: test failures
Set Bug forwarded-to-address to 'https://github.com/moby/moby/pull/45972'.

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

Bug#1041254: docker.io: FTBFS: test failures

[Shengjing Zhu]

Control: forwarded -1 https://github.com/moby/moby/pull/45972

On Sun, Jul 16, 2023 at 10:51 PM Sebastian Ramacher
 wrote:
>
> Source: docker.io
> Version: 20.10.24+dfsg1-1
> Severity: serious
> Tags: ftbfs sid trixie
> Justification: fails to build from source (but built successfully in the past)
>
> https://buildd.debian.org/status/fetch.php?pkg=docker.io&arch=amd64&ver=20.10.24%2Bdfsg1-1%2Bb4&stamp=1689240350&raw=0
>

FTR, it's caused by golang-1.20 1.20.6-1, a security patch release
which restricts http header.
Should be fixed by https://github.com/moby/moby/pull/45972

-- 
Shengjing Zhu

Processed: librubberband-dev: missing dependency on libfftw3-dev

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:ffmpeg
Bug #1041255 [librubberband-dev] librubberband-dev: missing dependency on 
libfftw3-dev
Added indication that 1041255 affects src:ffmpeg

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

Bug#1041255: librubberband-dev: missing dependency on libfftw3-dev

[Sebastian Ramacher]

Package: librubberband-dev
Version: 3.2.1+dfsg-5
Severity: serious
Control: affects -1 src:ffmpeg

$ pkgconf --modversion rubberband
Package fftw3 was not found in the pkg-config search path.
Perhaps you should add the directory containing `fftw3.pc'
to the PKG_CONFIG_PATH environment variable
Package 'fftw3', required by 'rubberband', not found

This issue causes ffmpeg to FTBFS. Please add the missing dependency on
libfftw3-dev.

Cheers
-- 
Sebastian Ramacher

Bug#1041254: docker.io: FTBFS: test failures

[Sebastian Ramacher]

Source: docker.io
Version: 20.10.24+dfsg1-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=docker.io&arch=amd64&ver=20.10.24%2Bdfsg1-1%2Bb4&stamp=1689240350&raw=0

=== Failed
=== FAIL: pkg/authorization TestAuthZRequestPluginError (15.01s)
time="2023-07-13T09:24:27Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz381024824/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz381024824%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 1s"
time="2023-07-13T09:24:28Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz381024824/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz381024824%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 2s"
time="2023-07-13T09:24:30Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz381024824/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz381024824%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 4s"
time="2023-07-13T09:24:34Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz381024824/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz381024824%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 8s"
authz_unix_test.go:51: Failed to authorize request Post 
"http://%2F%2Ftmp%2Fauthz381024824%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq":
 http: invalid Host header

=== FAIL: pkg/authorization TestAuthZRequestPlugin (15.00s)
time="2023-07-13T09:24:42Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3777015250/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz3777015250%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 1s"
time="2023-07-13T09:24:43Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3777015250/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz3777015250%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 2s"
time="2023-07-13T09:24:45Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3777015250/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz3777015250%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 4s"
time="2023-07-13T09:24:49Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3777015250/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz3777015250%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 8s"
authz_unix_test.go:83: Failed to authorize request Post 
"http://%2F%2Ftmp%2Fauthz3777015250%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq":
 http: invalid Host header

=== FAIL: pkg/authorization TestAuthZResponsePlugin (15.01s)
time="2023-07-13T09:24:57Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3358757484/authz-test-plugin.sock/AuthZPlugin.AuthZRes: Post 
\"http://%2F%2Ftmp%2Fauthz3358757484%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZRes\":
 http: invalid Host header, retrying in 1s"
time="2023-07-13T09:24:58Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3358757484/authz-test-plugin.sock/AuthZPlugin.AuthZRes: Post 
\"http://%2F%2Ftmp%2Fauthz3358757484%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZRes\":
 http: invalid Host header, retrying in 2s"
time="2023-07-13T09:25:00Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3358757484/authz-test-plugin.sock/AuthZPlugin.AuthZRes: Post 
\"http://%2F%2Ftmp%2Fauthz3358757484%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZRes\":
 http: invalid Host header, retrying in 4s"
time="2023-07-13T09:25:04Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3358757484/authz-test-plugin.sock/AuthZPlugin.AuthZRes: Post 
\"http://%2F%2Ftmp%2Fauthz3358757484%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZRes\":
 http: invalid Host header, retrying in 8s"
authz_unix_test.go:113: Failed to authorize request Post 
"http://%2F%2Ftmp%2Fauthz3358757484%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZRes":
 http: invalid Host header

=== FAIL: pkg/authorization TestMiddlewareWrapHandler/Positive_Test_Case_: 
(15.01s)
time="2023-07-13T09:25:27Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz2461853618/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz2461853618%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 1s"
time="2023-07-13T09:25:28Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz2461853618/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz2461853618%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 2s"
t

Bug#1041242: libheif1: 1.16.2-1+b1 breaks displaying any pictures

[Christoph Anton Mitterer]

On Sun, 2023-07-16 at 16:25 +0200, Fabian Greffrath wrote:
> Do you have the heif-gdk-pixbuf package installed? 

Yes:

On Sun, 2023-07-16 at 14:25 +0200, Christoph Anton Mitterer wrote:
> With libheif1, heif-gdk-pixbuf and heif-thumbnailer installed, I was


Cheers,
Chris.

Bug#1041253: pyside2: stop depending on qtwebengine5-dev on mipsel

[Sebastian Ramacher]

Source: pyside2
Version: 5.15.10-2
Severity: serious

qtwebengine-opensource-src currently FTBFS on mipsel (see #1041250). To
complete the currently ongoing Qt transition, please disable support for
qtwebeninge-opensource-src on mipsel for the time being. This would
allow us to (temporarily) remove qtwebengine-opensource-src from mipsel.

Cheers
-- 
Sebastian Ramacher

Bug#1041207: debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE

[Vagrant Cascadian]

On 2023-07-16, Simon McVittie wrote:
> On Sat, 15 Jul 2023 at 18:27:24 +0200, Adam Borowski wrote:
>> But, what matters here is the CTTE ruling in #1035831 -- for the time being,
>> packages must not move files between locations affected by the aliasing.
>
> If that happens in reality, then yes, that's bad, and reverting the change
> is a mitigation. What packages have this behaviour?
>
> We are going to need to bring back this change relatively early in the
> trixie cycle in any case, for the reasons given in the commit message.
> I have not yet analyzed whether we need this change before we can lift
> the moratorium on file moves, but I suspect we might.
>
>> Packages built in an usrmerged chroot place such files under /usr while
>> built without usrmerge into whatever place they were installed to -- which
>> is a direct breach of the ruling.
>
> Do you have examples of packages that differ in this way when built in
> a merged- or unmerged-/usr environment? I think we should treat this
> as a RC-for-trixie bug in those packages (and in fact I would have been
> tempted to call it RC for bookworm as well, again for the reasons given
> by the TC, even though during the trixie cycle it was mitigated by using
> unmerged-/usr fro buildds).
>
> During most of the bookworm cycle, https://reproducible-builds.org/ has
> been doing "build1" in unmerged-/usr and "build2" in merged-/usr, with
> differences tracked in
> 
> (that list is not necessarily complete, there can also be unidentified
> differences in
> ).

For what it is worth, there were various points during the bookworm
cycle where this was not being tested on reproducible builds
infrastructure, as the mechanisms to disable it changed several
times...

We used to just be able to build a non-usrmerge tarball, and then
install usrmerge in the second build, but I think usr-is-merged or some
similar package is installed out of the box now, and the inverse
operation is non-trivial.

... which lead to some of the identified issues being systematically
removed for packages that were otherwise reproducible (you could still
look through git history to find more, but some many may be actually
fixed).

There are differing opinions on weather reproducible builds test
infrastrure should test usrmerge variations at all, given the direction
of Debian, though any alternate test infrastructure would essentially
have to implement a reproducible builds style test to check for
differences...

After upgrading the infrastructure to bookworm, testing usrmerge
variations broke again, and so is currently disabled... though I have
configured the paths_vary_due_to_usrmerge issue so that old known issues
are not automatically removed anymore.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1041252: libksysguard: stop depending on qtwebengine5-dev on mipsel

[Sebastian Ramacher]

Source: libksysguard
Version: 4:5.27.5-2
Severity: serious

qtwebengine-opensource-src currently FTBFS on mipsel (see #1041250). To
complete the currently ongoing Qt transition, please disable support for
qtwebeninge-opensource-src on mipsel for the time being. This would
allow us to (temporarily) remove qtwebengine-opensource-src from mipsel.

Cheers
-- 
Sebastian Ramacher

Bug#1041242: libheif1: 1.16.2-1+b1 breaks displaying any pictures

[Fabian Greffrath]

Do you have the heif-gdk-pixbuf package installed? Von meinem/meiner Galaxy 
gesendet

Bug#1041250: qtwebengine-opensource-src: FTBFS on mipsel

[Sebastian Ramacher]

Source: qtwebengine-opensource-src
Version: 5.15.14+dfsg-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src&arch=mipsel&ver=5.15.14%2Bdfsg-3&stamp=1687417516&raw=0
https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src&arch=mipsel&ver=5.15.14%2Bdfsg-4&stamp=1688914864&raw=0
https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src&arch=mipsel&ver=5.15.14%2Bdfsg-5&stamp=1688996139&raw=0
https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src&arch=mipsel&ver=5.15.14%2Bdfsg-6&stamp=1689327354&raw=0

rm -f libQt5WebEngineCore.so.5.15.14 libQt5WebEngineCore.so 
libQt5WebEngineCore.so.5 libQt5WebEngineCore.so.5.15
g++ -Wl,-z,relro -Wl,--no-keep-memory -Wl,-z,now 
@/<>/src/core/release/QtWebEngineCore_o.rsp -Wl,--start-group 
@/<>/src/core/release/QtWebEngineCore_a.rsp -Wl,--end-group 
-Wl,-z,noexecstack -Wl,--fatal-warnings -Wl,--build-id=sha1 -fPIC -Wl,-z,relro 
-Wl,-z,now -Wl,-z,defs -Wl,--hash-style=sysv -mips32 -Wl,-O2 -Wl,--gc-sections 
-rdynamic -Wl,-z,relro -Wl,--no-keep-memory -Wl,-z,now -Wl,-O1 
-Wl,--enable-new-dtags -Wl,-whole-archive -lqtwebenginecoreapi 
-Wl,-no-whole-archive -Wl,--no-undefined 
-Wl,--version-script,QtWebEngineCore.version -Wl,-O1 -fuse-ld=gold 
-Wl,--enable-new-dtags -shared -Wl,-soname,libQt5WebEngineCore.so.5 -o 
libQt5WebEngineCore.so.5.15.14   /usr/lib/mipsel-linux-gnu/libQt5Quick.so 
/usr/lib/mipsel-linux-gnu/libQt5Gui.so 
/usr/lib/mipsel-linux-gnu/libQt5QmlModels.so 
/usr/lib/mipsel-linux-gnu/libQt5WebChannel.so 
/usr/lib/mipsel-linux-gnu/libQt5Qml.so 
/usr/lib/mipsel-linux-gnu/libQt5Network.so 
/usr/lib/mipsel-linux-gnu/libQt5Positioning.so 
/usr/lib/mipsel-linux-gnu/libQt5Core.so -lpthread -latomic -lGL -lpthread 
-latomic -ldl -lrt -licui18n -licuuc -licudata -lnss3 -lnssutil3 -lsmime3 
-lplds4 -lplc4 -lnspr4 -lz -levent -lresolv -ljpeg -lm -lopus -lvpx -lX11 
-lXcomposite -lXdamage -lXext -lXfixes -lXrender -lXrandr -lXtst -lgio-2.0 
-lgobject-2.0 -lglib-2.0 -lpng16 -lwebpmux -lwebpdemux -lwebp -lfreetype 
-lexpat -lfontconfig -lharfbuzz-subset -lharfbuzz -lre2 -lX11-xcb -lxcb 
-lxkbcommon -ldbus-1 -lpci -lasound -lsnappy -lxml2 -lxslt -lminizip -llcms2 
-lopenjp2 -L/<>/src/core/api/release -lGL   
/usr/bin/ld.gold: fatal error: libQt5WebEngineCore.so.5.15.14: mmap: failed to 
allocate 216082048 bytes for output file: Cannot allocate memory
collect2: error: ld returned 1 exit status
make[5]: *** [Makefile.core_module:90: 
../../lib/libQt5WebEngineCore.so.5.15.14] Error 1

Cheers
-- 
Sebastian Ramacher

Bug#1041249: cpp-httplib: FTBFS on s390x: ../test/test.cc:5462: Failure

[Sebastian Ramacher]

Source: cpp-httplib
Version: 0.13.1+ds-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=cpp-httplib&arch=s390x&ver=0.13.1%2Bds-1&stamp=1689418150&raw=0

[--] 1 test from InvalidScheme
[ RUN  ] InvalidScheme.SimpleInterface
[   OK ] InvalidScheme.SimpleInterface (0 ms)
[--] 1 test from InvalidScheme (0 ms total)

[--] 1 test from NoScheme
[ RUN  ] NoScheme.SimpleInterface
[   OK ] NoScheme.SimpleInterface (0 ms)
[--] 1 test from NoScheme (0 ms total)

[--] 1 test from ClientImplMethods
[ RUN  ] ClientImplMethods.GetSocketTest
[   OK ] ClientImplMethods.GetSocketTest (4 ms)
[--] 1 test from ClientImplMethods (4 ms total)

[--] 1 test from HttpToHttpsRedirectTest
[ RUN  ] HttpToHttpsRedirectTest.CertFile
../test/test.cc:5462: Failure
Value of: res
  Actual: false
Expected: true
==


Summary of Failures:

1/1 main TIMEOUT900.25s   killed by signal 15 SIGTERM


When starting an uncoordinated transition, please at least ensure that
the package at least builds on all suported platforms.

Cheers
-- 
Sebastian Ramacher

Processed: fixed 1036281 in 0.21.1-4

[Debian Bug Tracking System]

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

> fixed 1036281 0.21.1-4
Bug #1036281 {Done: Salvatore Bonaccorso } [src:libraw] 
libraw: CVE-2023-1729
Marked as fixed in versions libraw/0.21.1-4.
> thanks
Stopping processing here.

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

Bug#1037538: gerbera: FTBFS with libupnp17

[Sebastian Ramacher]

On 2023-07-15 01:43:03 +0200, Bastian Germann wrote:
> On Tue, 20 Jun 2023 21:17:01 +0200 Bastian Germann wrote:
> > This is the last package that prevents fulfilling the pupnp transition.
> > Would you please go ahead with a team upload? I do not think James is still 
> > around.
> 
> I have prepared a NMU with a new upstream version:
> https://salsa.debian.org/multimedia-team/gerbera/-/merge_requests/1
> 
> If nobody objects I am going to upload it soon.

Please go ahead

Cheers
-- 
Sebastian Ramacher

Bug#999926: marked as done (xfce4-verve-plugin: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 12:51:14 +
with message-id 
and subject line Bug#26: fixed in xfce4-verve-plugin 2.0.3-1
has caused the Debian Bug report #26,
regarding xfce4-verve-plugin: depends on obsolete pcre3 library
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.)


-- 
26: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=26
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfce4-verve-plugin
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Source: xfce4-verve-plugin
Source-Version: 2.0.3-1
Done: Yves-Alexis Perez 

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-verve-plugin 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Jul 2023 14:02:45 +0200
Source: xfce4-verve-plugin
Architecture: source
Version: 2.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 26
Changes:
 xfce4-verve-plugin (2.0.3-1) unstable; urgency=medium
 .
   * d/control: build against libpcre2 (Closes: #26)
   * New upstream version 2.0.3
   * d/control: update standards version to 4.6.2
Checksums-Sha1:
 213c7068fb4b157c6f5fd6c8fa6f7ba7170d9f9d 1799 xfce4-verve-plugin_2.0.3-1.dsc
 6d1f94c903a173c68d37f25618a37cf624f6b7e2 383536 
xfce4-verve-plugin_2.0.3.orig.tar.bz2
 6f8327d0a16def8a9f61be6dc8496b81fbbde572 3380 
xfce4-verve-plugin_2.0.3-1.debian.tar.xz
 c054671e346ca21b9e90a1b9252e2fd0078cb431 15680 
xfce4-verve-plugin_2.0.3-1_amd64.buildinfo
Checksums-Sha256:
 dd0699a5ecde084a0992d91faa11f01e28261ee291cf4ccbe84a3809d966d21b 1799 
xfce4-verve-plugin_2.0.3-1.dsc
 e1bf121f1bf9cf2a199bf5c0f3aa802f503df9bea50724741e7a92fe6d9fe09e 383536 
xfce4-verve-plugin_2.0.3.orig.tar.bz2
 5f4449c2cc9078797f03688454284ce020e06e997959b6e30de05050fdd661ba 3380 
xfce4-verve-plugin_2.0.3-1.debian.tar.xz
 4a754bde6194a57df0b9d0c57bdecfe56675d1991bc2975a19ea7b85da9f5e36 15680 
xfce4-verve-plugin_2.0.3-1_amd64.buildinfo
Files:
 ed3d0a41596b0c63ee4eeff6f14eb122 1799 xfce optional 
xfce4-verve-plugin_2.0.3-1.dsc
 7dac12f16b09031c985fe71e4e599377 383536 xfce optional 
xfce4-verve-plugin_2.0.3.orig.tar.bz2
 ebd0598dc841aa0a9c940533563cf6f6 3380 xfce optional 
xfce4-verve-plugin_2.0.3-1.debian.tar.xz
 b65dadbe734057bc7bc5d316533a6d84 15680 xfce optional 
xfce4-verve-plugin_2.0.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSz3r8ACgkQ3rYcyPpX
RFurxQf/YA+z2aLqXZPeU+LywYDlxX0tqyEKa/i05CY8xSS2GwZORu+xbLyElCH5
28kYDGk9BIkMMYlkkuhyMqihFUZWulpkZVnGlcW5tNbzQAWoIvjonQep7FFdTMFo
dXDCN6G1WblEe5Kx/fzf6QZo5BxiqXGge+54nrKXwHjkjk1I/f6nqBGr8qpIPEkE
NammGpERV430x2sIZxAgnFwZKETiwxc47x/fz6yoYK6f8tLyMQ7OvQ8faGrG3ImN
tk0DHLH/Sz34KvyZeJsbSRHGiMva1gAmlNmoqn0P/wOQd9+q2z/EacvMVBv+eDgZ
tikPuUNwwW3QE7UtrKSViUBLRutgYg==
=Vuga
-END PGP SIGNATURE End Message ---

Bug#1041233: [Pkg-rust-maintainers] Bug#1041233: librust-heapless-dev: impossible to install: depends on missing package librust-heapless-0.7-dev

[Peter Michael Green]

As subject says, this package depends on librust-heapless-0.7-dev which
is missing, rendering the package impossible to install.

I don't see any such dependency, was this a typo.

It does however seem to depend on librust-defmt-0.3+default-dev,
rust-defmt hasn't been uploaded yet, but it seems Alexander Kjäll
is working on it.

Bug#1041233: [Pkg-rust-maintainers] Bug#1041233: librust-heapless-dev: impossible to install: depends on missing package librust-heapless-0.7-dev

[Jonas Smedegaard]

Quoting Peter Michael Green (2023-07-16 14:46:40)
> > As subject says, this package depends on librust-heapless-0.7-dev which
> > is missing, rendering the package impossible to install.
> I don't see any such dependency, was this a typo.

Ah, right, silly me.

 - 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

Bug#1041117: marked as done (dde-network-utils FTBFS with googletest 1.13.0)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 12:36:15 +
with message-id 
and subject line Bug#1041117: fixed in dde-network-utils 5.4.13-2
has caused the Debian Bug report #1041117,
regarding dde-network-utils FTBFS with googletest 1.13.0
to be marked as done.

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

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


-- 
1041117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dde-network-utils
Version: 5.4.13-1
Severity: serious
Tags: ftbfs trixie sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dde-network-utils.html

...
In file included from /usr/include/gtest/gtest-message.h:57,
 from /usr/include/gtest/gtest-assertion-result.h:46,
 from /usr/include/gtest/gtest.h:64,
 from tst_networkmodel.cpp:1:
/usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less 
than C++14 are not supported.
  270 | #error C++ versions less than C++14 are not supported.
  |  ^
...


This can be fixed by changing c++11 to c++14
in tests/dde-network-utils/tst_dde-network-utils.pro
--- End Message ---
--- Begin Message ---
Source: dde-network-utils
Source-Version: 5.4.13-2
Done: Nisha Pariyar 

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

Debian distribution maintenance software
pp.
Nisha Pariyar  (supplier of updated dde-network-utils 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Jul 2023 15:43:37 +0545
Source: dde-network-utils
Architecture: source
Version: 5.4.13-2
Distribution: unstable
Urgency: medium
Maintainer: Arun Kumar Pariyar 
Changed-By: Nisha Pariyar 
Closes: 1041117
Changes:
 dde-network-utils (5.4.13-2) unstable; urgency=medium
 .
   * debian/patches: Fix ftbfs by removing explicit cxx11. (Closes: #1041117)
   * debian/control:
 + Bump standard version to 4.6.2.
 + Add myself to uploaders list.
Checksums-Sha1:
 804de1f7f841d427f288531d4640cbd8ef3fa2cd 2400 dde-network-utils_5.4.13-2.dsc
 a2a607cf1c4a0f8461ffa851d5f48bd2bf92be39 3736 
dde-network-utils_5.4.13-2.debian.tar.xz
 636eade2092b05e57b143b7bb2dee4916d703cff 12307 
dde-network-utils_5.4.13-2_amd64.buildinfo
Checksums-Sha256:
 1c6eb3d754ef675b6629acf4e399f9b703fb46e95cbe085da0e4d14d62acda4a 2400 
dde-network-utils_5.4.13-2.dsc
 59f91b8f9d0cfa34ce5c7ce3a9f4bb8b7d665840cf2e99cccbd23a1f3bf7226f 3736 
dde-network-utils_5.4.13-2.debian.tar.xz
 f23fa38b67cf4b68777a766b87b5a68e9e620d5b29306f10db2dacf3a0956c0c 12307 
dde-network-utils_5.4.13-2_amd64.buildinfo
Files:
 d58dca28952d2eb647fd8a300019943f 2400 libs optional 
dde-network-utils_5.4.13-2.dsc
 e873a177d3a8ea5af3e4dd9bb213cc9e 3736 libs optional 
dde-network-utils_5.4.13-2.debian.tar.xz
 70dc16e90238b72eac6410a6e4de4da5 12307 libs optional 
dde-network-utils_5.4.13-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE2lMFjb4VS9/L8WutS1Qq9wT3RRYFAmSz3LoACgkQS1Qq9wT3
RRZAyA//c6KLb10e39fOAnaSiS6O+zytkiM69QezV0WUsWqcVbSe4t4bFOt1cXIM
oRPZH7BG8uSklA90FCR6TYHSRs2dKQrrBsEMGy79Im7OxKpGwokwTYKG7F0Sw5H0
J9pPo6SUv4z3l20Mw/pZxjwOhbe9ls2DbxCZcMN16jUSxHoUzDFkMbCIAUChGggm
LKEPGtB2+zjXkPSkutKwWdymBvwS4cU2lfRiT/tYHPcP0UpOy7tV1qtoWPF/Ub2X
HdaRcwZvjErVJmV0GZnwWuHwezoxdF59at0O1tx3ybSg1mezE2cMLNpsVYmCkhYa
2/0JiLpRzFmsMcs5dp3Bq+h8+ztHOGkZOgAyKjSgC5GniVoxMdwIVrW7ysQUyBt7
TMtlAscwnaEwROih1WilcBEeuVcKeS+kkImohPCEFp471o+/r8ptNzn6GZ1gaZYB
VZCi4IIlfXDE8EKuqPy6hXsLUpXzqM0gcsrG09jmMHqgdsS0vcecwwsQ5ycOM13x
xQVvd8CFBAx4B86DCIly4qbJVmPBIF8XlhgOfXqP5mEugnDaHYk5Dmu7zjzbOKSj
5ypu1NNu2kZiLy5yLhpQu0WMemwn/6ipyj9carJBT5o3FhqA1UeTlsV2I1dkL/wv
CFWcFa6LFtv5GJ7F4TeLx388EG4wDbKyKJ1nCXe1pi0EST0Vyxw=
=vqYs
-END PGP SIGNATURE End Message ---

Bug#1041242: libheif1: 1.16.2-1+b1 breaks displaying any pictures

[Christoph Anton Mitterer]

Weird... I did another upgrade/downgrade cycle and it now works (with
the downgraded version) for eog too.

And I'm pretty sure I checked the first time, whether eog was perhaps
still running and using the old (that is the new version) of the lib.